Epic Goal

Install GH in a brownfield without any degrade for the existing ACM features.

Why is this important?

• Save cost: do not need to setup from scratch
• Easy to adopt

Scenarios

• I have a ACM hub. And I want to install Fabric on the same cluster (because I want Authz and Inventory and Kafka messages and Change history)
• I have a ACM hub, I want to integrate with ACS to show the security information

Acceptance Criteria

...

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 - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.