[
https://issues.apache.org/jira/browse/KNOX-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-2358:
--------------------------------
+Apache Knox 3.0.0 release preparation+
We are about to cut the 3.0.0 release branch. master will move on to 3.1.0.
This issue is currently unresolved and is not automatically included in 3.0.0.
Please choose one of the following:
# If this belongs in 3.0.0: once the branch is cut, cherry-pick your commit(s)
onto the new v3.0.0 branch in addition to master. Leave Fix Version = 3.0.0 so
we can track it.
# Do nothing: we will move this issue to the next release (3.1.0) as part of
release cleanup.
If we don't hear back and see no cherry-pick, the issue will be re-targeted to
3.1.0. Thanks!
> Reload the Knox Home page upon topology changes
> -----------------------------------------------
>
> Key: KNOX-2358
> URL: https://issues.apache.org/jira/browse/KNOX-2358
> Project: Apache Knox
> Issue Type: Improvement
> Components: Homepage
> Affects Versions: 1.4.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Minor
> Fix For: 3.0.0
>
>
> It would be nice if the Knox home page got reloaded when Knox redeploys a
> topology. Using push notifications seems to be a good way to do this.
> Alternatively, a client-side poll can be configured to fetch changes from the
> Knox back-end.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
