[patch] Add support for adoption metrics reporting flag in ansible #1959
+10
−0
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.
Issue
MASCORE-10350
Description
PI compliance and Opt-out for Consumability metrics
This PR adds support for the new reportAdoptionMetrics flag in the Ansible to align with the MAS opt-out feature.
The flag allows users to control whether Account Adoption Metrics are sent to IBM. These metrics help assess MAS adoption and product usage but are completely optional.
When the playbook is executed, this parameter value flows into the Suite CR under spec.settings.reportAdoptionMetrics.
Set default value to true (enabled by default).
Integrated with the “Adoption Metrics Reporting” system setting in the Suite CR, configurable from the Admin UI.
Test Results
Executed the ansible play book on the cluster. Verified that the reportAdoptionMetrics value is correctly reflected in suite CR.
