-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(common): adding rbac support #354
Conversation
I'm going to merge the PR as-is into the 3.5.0 branch, but I'm not sure if I'll keep the |
In retrospect I guess the object-specific enrichment could be moved into the |
Description of the change
"bjw-s.common.lib.valuesToObject"
with the purpose of eventually migrating all repeated*.valuesToObject
templates to this.Removed
Fixed
Added
common.valuesToObject
template you now can use theforceRename
field to completely ignore the naming convention of your generated resourcesChanged
Benefits
rawResources
forceRename
field can allow for a seamless transition between your previously existing resources and the ones created by the chart (useful if, for instance, you're using ArgoCD and don't want it to delete your old resource and recreate it with a different name)Possible drawbacks
Applicable issues
Additional information
getByIdentifier
templateChecklist
Chart.yaml
has been bumped according to Semantic Versioning.artifacthub.io/changes
changelog annotation has been updated inChart.yaml
. See Artifact Hub documentation for more info.values.yaml
file.