Skip to content

Conversation

@cadenmarchese
Copy link
Collaborator

Which issue this PR addresses:

Fixes no jira

What this PR does / why we need it:

  • We store a local copy of our current role sets for dev cluster purposes. The real copy lives in RP-Config.
  • I wanted to update what was there since it's out of date, but since the role set has been consistent across versions (so far), I converted the role set to YAML so that we can use anchoring and get rid of some of the duplication.
  • We can't use a single role set for all versions since role sets are version-specific and expected to evolve with OCP.
  • The RP still expects JSON role sets so render it out to JSON using yq

Test plan for issue:

  • Ran the script locally to confirm it works.

Is there any documentation that needs to be updated for this PR?

No - end functionality doesn't change.

How do you know this will function as expected in production?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chainsaw Pull requests or issues owned by Team Chainsaw

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants