Closed
Conversation
Signed-off-by: Neil South <neil.south@answerdigital.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
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.




Sensitive Credential Checks
Motivation and Context
Improving the documentation to allow an easier setup for new devs to the project.
Description
aligned the keycloak client name used for local deployment, now its consistently "management-node".
Fix up curl commands to now pass necessary certs.
Added missing Keycloak Realm file for import
Improved documentation around creation of this realm, if not importing it.
How Has This Been Tested?
Ran though the Readme again and followed the implementation to ensure correct outcome, this was done on a Windows 11 machine under WSL2.
Checklist: