Allow static registration instead of eureka if desired#358
Open
1000TurquoisePogs wants to merge 3 commits intov3.x/stagingfrom
Open
Allow static registration instead of eureka if desired#3581000TurquoisePogs wants to merge 3 commits intov3.x/stagingfrom
1000TurquoisePogs wants to merge 3 commits intov3.x/stagingfrom
Conversation
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a feature in which app-server can use static registration to apiml instead of eureka.
This is not preferred, but if users are not doing HA, and are experiencing unresolved connection issues, this could be a workaround to help get them going?
Requires zowe/zlux-server-framework#654
You can test this by changing property components.app-server.node.mediationLayer.static: true/false
false is default.
When true, an app-server yaml is written to workspace/api-medation/api-defs
When false, it is removed.
Either way, app-server should show up on the catalog and be accessible from the gateway.
There is a small issue that if app-server is later disabled, it does not have opportunity to do cleanup of the workspace.