removed contextpath from zeebeGateway management port #1795
Conversation
This file contains 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
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.
Which problem does the PR fix?
closes #1789
What's in this PR?
Context: https://camunda.slack.com/archives/CSQ2E3BT4/p1714396844039029
This PR removes the
zeebeGateway.contextPathconfiguration from the management port, making it serve the actuator as well as prometheus on root (/) againNow, I faced the issue that if the context path of zeebeGateway is set to
/zeebe, console will not work properly...Checklist
Please make sure to follow our Contributing Guide.
Before opening the PR:
make go.update-golden-only.Comment: this PR changes the same file: #1672
After opening the PR: