Epic Goal

• ACM Create an Ansible-Collection to Consume RHACM. This Collection

The Ansible-Kubernetes-Collection is Nr 2 most downloaded collections. While RHACM-Ansible-Collection will reuse all those concepts we need
to implement further logic to implement RHACM specific functionality.

Here is a list of things (order in priority) which need to be implemented

• Manager Connectivity
• Manage Credentials

for the end-goal to allow users preexisting playbooks

Focus should be to reuse a

• Provision-Clusters (OpenShift, Kubernetes)
• import-Clusters
• Deploy-Applications
• Deploy-Policies
• Monitor the ACM-Clusters

Why is this important?

• …

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

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>