nexusRepositoryManager update to 72.0.0-bb.1

Package Merge Request

Package Changes

https://repo1.dso.mil/big-bang/product/packages/nexus/-/blob/72.0.0-bb.1/CHANGELOG.md

Package MR

big-bang/product/packages/nexus!193 (merged)

For Issue

Closes big-bang/product/packages/nexus#145 (closed)

Upgrade Notices

N/A

added botmr nexusRepositoryManager statusdoing labels

assigned to @nbazzeghin

changed the description

requested review from @chris.oconnell, @michaelmartin, and @andrewshoell

changed the description

marked this merge request as ready

added statusreview label and removed statusdoing label

changed milestone to %2.39.0

@nbazzeghin . I like what we've done here to enable the realms on the fly.

It seems like we've re-purposed a single "sso.realm" name to now mean a "list of realms to enable" . Some realms that can be enabled --e.g. DockerToken -- are not sso related. So, it's confusing that would be defined under an sso key -- especially if sso is not enabled.

Could we:

1. Refactor sso.realm to a top-level realms:key. And then use the logic you added to enable the list of realms there.
2. Keep sso.realm to specify the "realm name" to be used by default for Big Bang SSO installs. This name would then be added to the top-level realms: list.

I don't think that should be too much work, but I think that would help make the values a little clearer in what's being done.

requested review from @troymobley and @cbowmanclare

mentioned in issue big-bang/product/packages/nexus#148 (closed)

resolved all threads

approved this merge request

merged

mentioned in commit 16282f6a

mentioned in merge request big-bang/customers/template!107 (merged)