Add playbooks to manage configuration files #784
Merged
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.
What does this PR do?
Adds two playbooks to ease the management of the configuration files:
rename_objects.yaml
: If there's a need of renaming one credential (for example), this playbook can be used to rename the credential itself and update all the Job Templates / Workflows / Organizations... that are using the old credential name to the new one.set_organization.yaml
: If you need to set the organization name for all the objects contained in a path, this playbook will do the job easy.How should this be tested?
This can be applied to any path populated with CasC content. Each playbook has an execution example in the last line of the file.
Is there a relevant Issue open for this?
N/A
Other Relevant info, PRs, etc
N/A