[
https://issues.apache.org/jira/browse/KNOX-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774131#comment-17774131
]
ASF subversion and git services commented on KNOX-2962:
-------------------------------------------------------
Commit 1eeaf7315372bd7f8592e828dcac61740ba64581 in knox's branch
refs/heads/master from Attila Magyar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=1eeaf7315 ]
Revert "KNOX-2962 - Knox readiness check gateway-status endpoint should return
the list of topologies for which it is waiting for (#800)" (#803)
This reverts commit ff6bcbcac5c5d0e8f00f4944207975f5b1bfeebf.
> Knox readiness check gateway-status endpoint should return the list of
> topologies for which it is waiting for
> --------------------------------------------------------------------------------------------------------------
>
> Key: KNOX-2962
> URL: https://issues.apache.org/jira/browse/KNOX-2962
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: J.Andreina
> Assignee: Attila Magyar
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Current behaviour :
> Knox readiness api return only no/pending as the status . Hence when there is
> any issue with any custom topology deployment
> "https://localhost:8443/gateway/health/v1/gateway-status"; is invoked , it
> shows status as only PENDING . User have to check the gateway.log file to
> understand what are topologies it is waiting for to be deployed
> Expectation :
> If "https://localhost:8443/gateway/health/v1/gateway-status"; is PENDING
> should return the list of topology for which it is waiting for .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
