ROX-19330: Add second declarative config mount point to central CR #1223
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.
Description
This PR adds a second declarative config mount point to ACSCS centrals.
The secret referenced here will not be created by reconciler, but rather manually and only when customer requests multiple orgs support. In that case
cloud-service-manual-declarative-configs
secret will be created and populated with the corresponding auth provider configuration.The reasons to introduce separate secret here:
cloud-service-sensible-declarative-configs
contents are controlled only byfleetshard-sync
, let's keep it that wayIdeally, I would like to name secrets
cloud-service-reconciled-declarative-configs
andcloud-service-manual-declarative-configs
, however, migrating existing secret names looks like a non-trivial task not worth pursuing.Checklist (Definition of Done)
Test manual
ROX-12345: ...
Test manual