✨ Parametrize filename for generated RBAC #1169
Merged
+13 −1
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.
Before this change, the file name of the role/clusterrole generated from
+rbacmarkers was hardcoded torole.yaml.This change introduces a parameter
fileNameto the RBAC generator, so that one can doand have the file be
my-rbac-my-choice.yamlinstead. (Given no specifiedoutputin the above example, the full path of the output file will be/config/rbac/my-rbac-my-choice.yaml.)This is useful e.g. in cases where the target directory structure is not the standard Kustomize-packaged Kubebuilder one, but instead e.g. a Helm chart where multiple sources of information may contribute to the final set of files.