Nexus role mapping
Summary
Nexus-Repository-Manager additional feature: This addition to Big Bang Nexus allows the user to add multiple roles when nexus is enable for the first time as an addon within Big Bang. addons.nexus.sso is required to be enabled An activate nexus license key is required
Merge request reports
Activity
added nexus label
added 1 commit
- 65efa612 - renamed nexus.sso.role to nexus.role, added flag
added 74 commits
-
dd059d1c...8d8b987b - 73 commits from branch
master - c8070e6e - Merge remote-tracking branch 'origin/master' into nexus-role-mapping
-
dd059d1c...8d8b987b - 73 commits from branch
After merging Master into the branch "Nexus Role Mapping", Kiali failed the helm test after the pipeline finished running.
Kiali Helm test failing is a known issue within Big Bang.
https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/875
Edited by rarencibiaadded statusreview label
requested review from @micah.nagel and @ryan.j.garcia
-
I'm not sure the best way to tackle this but could we keep the default behavior that we had before if someone does not provide anything in
addons.nexus.sso.role? If I'm tracking the changes right previously we just made a single role for all keycloak users as admins, and with these changes we make it so there is no default role but users can specify multiple. Definitely like the addition, but I am always wary of changing values/breaking default behavior from previous releases...
added statusdoing label and removed statusreview label
mentioned in merge request !1034 (merged)
Resolved by kevin.wilderI have a competing/overlapping MR to address all the Nexus templating issues.
https://repo1.dso.mil/platform-one/big-bang/bigbang/-/merge_requests/1034
I will incorporate your range templating for multiple roles in my MR.- Last reply by kevin.wilder
-
!1034 (merged) is merged. This MR can be closed.