OCP/Telco Definition of Done
Epic Template descriptions and documentation.

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

Epic Goal

ClusterExtensions apply (or deletes) a set of resources to the cluster. The same resources might already exist on the cluster, creating a possible conflict situation.

Why is this important?

Un/installation is  a fundamental feature of OLM. Therefore, we should explore the different possible error cases and ensure they are appropriately handled.

Scenarios

1. The user creates a new ClusterExtension that contains resources already present on the cluster, but not managed by OLM. In this case, OLM is allowed to adopt the resource and take over its management.
2. The user deletes an existing ClusterExtension, but one or more resources referenced in the bundle are not managed by OLM. In this case, deletion should fail with an appropriate condition and informative message

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. Upstream parent issue: https://github.com/operator-framework/operator-controller/issues/736 

Open questions::

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>