We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Service ID's of Catalog and Discovery are not consistent with the Gateway and active configuration.
Expected behavior The service ID's will replicate the configured hostnames. instance.env like this:
instance.env
APIML_GATEWAY_EXTERNAL_MAPPER=https://zhaplex.svl.ibm.com:57554/zss/api/v1/certificate/x509/map APIML_SECURITY_AUTHORIZATION_ENDPOINT_URL=https://zhaplex.svl.ibm.com:57554/zss/api/v1/saf-auth ZOWE_EXPLORER_HOST=tivlp14.svl.ibm.com ZWE_EXTERNAL_HOSTS=zhaplex.svl.ibm.com,9.30.238.45 ZWE_REFERRER_HOSTS=zhaplex.svl.ibm.com,9.30.238.45
Additional context Seems like our fix for this problem on Gateway is really just for Gateway 6b8c38a
The text was updated successfully, but these errors were encountered:
#1473
Sorry, something went wrong.
Solved in this PR: #1473 Will be available starting from API Layer V1.22.2
One more update to the naming for the API catalog will be available starting from 1.22.3-SNAPSHOT
1.22.3 contains all the necessary changes. I am closing the issue now.
balhar-jakub
No branches or pull requests
Describe the bug
Service ID's of Catalog and Discovery are not consistent with the Gateway and active configuration.
Expected behavior
The service ID's will replicate the configured hostnames.
instance.env
like this:Additional context
Seems like our fix for this problem on Gateway is really just for Gateway
6b8c38a
The text was updated successfully, but these errors were encountered: