FIX resolve #822 changing cm to secret#161
Conversation
Signed-off-by: Ryan Cook <rcook@redhat.com>
|
@Ladas right, we should not have keycloak admin secret be in the |
|
@cooktheryan I think follow up PR is good, because this is pre-existing issue? |
|
@cooktheryan yes, looks good to me. |
|
But let's check also with the AuthBridge team as @mrsabath is doing also changes in this area. |
|
Thank you @cooktheryan for these changes. They are good, but they will affect the current demo we are trying to build. I propose we close on the demo work first, since it turned out to be more work that we initially anticipated (see epic #173 ) and once that is finally working successfully, we should merge this PR on the top of it. Are you OK with this approach? |
Testing UpdateThe epic #173 (end-to-end demo validation) is now complete and all related PRs are merged. I've tested this PR locally with the following results: Conflict Resolution:
E2E Verification:
Note: The PR has conflicts with current @cooktheryan LGTM from the AuthBridge side. The conflicts are due to recent demo/webhook changes that landed while the PR was waiting. |
|
@mrsabath I'm good with moving forward to your rebase. Massive respect for the review, testing and rebase. You rock! |
fix: move Keycloak admin credentials from ConfigMap to Secret (rebased #161)
|
Closing -- all changes from this PR are included in the merged #179 (rebased version). Verified that every change from @cooktheryan's original commit is on main:
Thank you @cooktheryan for the original contribution! |
Summary
Rather than storing keycloak creds in CM it should use a secret
Related issue(s)
rossoctl/rossoctl#822
(Optional) Testing Instructions
Fixes #
rossoctl/rossoctl#822