PILOT-4319: update config file to allow user customize the api_url and keycloak_url - #121
Merged
Conversation
…rl instead of domain only
Contributor
andricDu
approved these changes
Dec 20, 2023
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
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.
Summary
Currently the config file only allows user to modify the domain name for keyloack/api endpoints. While with tenant based implementation, the url might vary based on the project as:
iam. It might contain regional prefix egca-iam.pilot.Upon requirements, update the config file to allow user add
api_urlandkeycloak_url:api_url: the url that the api server is hosted on. default ishttps://api.pilot.indocresearch.com/pilotkeycloak_realm_url: thr url that the keycloak server is hosted on. default ishttps://iam.pilot.indocresearch.com/realms/pilotdomain@colorzzr will need to update the
.envfile in the zipped bundleJIRA Issues
PILOT-4319
Type of Change
Please delete options that are not relevant.
Testing
Are there any new or updated tests to validate the changes?
Test Directions
(Additional instructions for how to run tests or validate functionality if not covered by unit tests)