[minor] Support Adoption Metrics Reporting Flag in GitOps Automation #1857
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Details
Introduce a new adoption metrics reporting opt-out flag in GitOps automation used by the SRE team to provision MAS SaaS clusters for customers. This flag is already being implemented in Ansible DevOps and the MAS CLI (separate functions from GitOps automation) and corresponding updates are now required in the GitOps pipeline to ensure consistent configuration management across all provisioning workflows. The changes made in this PR are strictly for the changes needed for GitOps automation.
Test Evidence
See https://github.ibm.com/maximoappsuite/saas-tekton/pull/167 for testing evidence.