[
https://issues.apache.org/jira/browse/KNOX-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291130#comment-16291130
]
Phil Zampino commented on KNOX-1131:
------------------------------------
At gateway startup:
* The relationships among existing provider configurations and descriptors must
be completely determined (KNOX-1144).
* Existing simple descriptors
** For each existing descriptor in conf/descriptors, compare the timestamp of
the descriptor with the corresponding topology file in conf/topologies
*** If there is no corresponding topology file, then generate and deploy one.
*** If there is a corresponding topology file, and its timestamp is more recent
than the descriptor, do NOT regenerate it.
*** If there is a corresponding topology file, and its timestamp is older than
the descriptor, regenerate and redeploy it.
> Review Gateway Startup Behavior WRT Deployment of Descriptors and Topologies
> ----------------------------------------------------------------------------
>
> Key: KNOX-1131
> URL: https://issues.apache.org/jira/browse/KNOX-1131
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.14.0
> Reporter: Phil Zampino
> Assignee: Phil Zampino
> Fix For: 0.15.0
>
>
> We need to review the behavior wrt simple descriptors and topologies
> concerning their (re)deployment. This behavior should be consistent and
> predictable.
> Upon gateway restart, what gets regenerated/redeployed? Anything? Nothing? If
> something, how to determine which ones?
> The current behavior may be correct, but it would be good to understand the
> totality of that behavior, and make adjustments where necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
