OCP/Telco Definition of Done
<https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde>
Epic Template descriptions and documentation.
<https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit>
ACM-wide Product Requirements (Top-level Epics)
<https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit>

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

Address customer misconfigurations and deployment issues by validating and where possible, enforcing the required configurations using ACM policies.

Improve the BusinessContinuity component by adding scenario validation using ACM policies.

Why is this important?

Most of the customer issues we were working with had the root cause in creating invalid configurations. Most of them can be flagged by a policy template and by doing that we not only reduce support costs but also make the user confident that their configuration is verified to be compliant and validated against rules that can be audit  and provide accountability for invalid configurations.

Scenarios

Add policy templates to validate hub DR settings, such as

• when MCH is initially created, backup is not enabled; add a policy to inform that the backup is not yet configured
• auto import configurations ( flag missing MSA secrets, add backup labels to MSA secrets, etc )
• OADP deployment - we had many issues where OADP was manually deployed at a version different than the one installed by ACM ; or had 2 OADP versions on the cluster, as different version - validate this using a policy template
•  

Acceptance Criteria

New policy templates created to validate above scenarios are running and reporting on hub DR config issue

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>