[patch] fix automated initial user creation when Manage is not installed #305
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
After the automated initial user creation feature was merged to
gitops:main
(#278) an issue was discovered in fvtsaas where the newpostsyncjobs
ArgoCD application would fail to sync on MAS instances where Manage is not installed (which may be the case <9.1.x) due to themas-xxx-manage
namespace not being present.This PR fixes this issue by only creating the Manage-related RBAC resources when Manage is actually installed.
Testing
Verified that the
postsyncjobs
application now syncs successfully and functions as expected in a 9.0.x env without ManageVerified that the
postsyncjobs
application still functions as expected (Manage RBAC resources created) in envs that do have Manage: