Skip to content
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

build: start tracking rbac generated from helm chart #8878

Merged
merged 1 commit into from
Sep 30, 2021

Conversation

BlaineEXE
Copy link
Member

This is a starting step to be able to generate common.yaml from Helm
charts. For right now, we merely want to be able to determine when the
rendered output of the Helm chart changes.

Signed-off-by: Blaine Gardner blaine.gardner@redhat.com

Description of your changes:

Which issue is resolved by this Pull Request:
Resolves #

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
  • Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
  • Reviewed the developer guide on Submitting a Pull Request
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.
  • Pending release notes updated with breaking and/or notable changes, if necessary.
  • Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
  • Code generation (make codegen) has been run to update object specifications, if necessary.

.github/workflows/helm-generate-rbac.yaml Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Makefile Show resolved Hide resolved
@BlaineEXE BlaineEXE force-pushed the initial-generate-rbac-from-helm branch 9 times, most recently from 6603fd1 to fc2edf9 Compare September 30, 2021 14:46
This is a starting step to be able to generate common.yaml from Helm
charts. For right now, we merely want to be able to determine when the
rendered output of the Helm chart changes.

Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
@BlaineEXE BlaineEXE force-pushed the initial-generate-rbac-from-helm branch from fc2edf9 to e2ba16f Compare September 30, 2021 18:20
@@ -0,0 +1,1239 @@
kind: ClusterRole
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other generated resources like crds.yaml are just generated directly to the location where they are needed such as the examples folder. Perhaps in a future PR, will this be directly generated directly to common.yaml?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the idea. For now I want to have some room to modify the helm charts and massage things into place in smaller PRs, then start generating common.yaml once things are in good shape rather than trying to change too much at once.

@BlaineEXE BlaineEXE merged commit 7aa4bbf into rook:master Sep 30, 2021
@BlaineEXE BlaineEXE deleted the initial-generate-rbac-from-helm branch September 30, 2021 19:49
@parth-gr
Copy link
Member

parth-gr commented Oct 4, 2021

@BlaineEXE, A question, I need to explicitly install this dependency pip install ruamel_yaml for running make gen-rbac.
Should we have an implicit installation or it is intended to work like this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants