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

Create AWS tags for machine pool on cluster creation time (day 1) and post-cluster creation time (day 2) on ROSA Classic.  Modification of AWS tags are out-of-scope.

• Hive to support additional list of key=value strings on MachinePools
  • These are AWS user-defined / custom tags, not to be confused with node labels
  • OCM/rosa CLI can accept a list of key=value strings with additional tag values
  • The default tag is still applied
  • NOTE: AWS limit of 50 tags per object (2 used automatically by OCP; with a third to be added soon) - customer's can only specify 47 tags max!
    • Source: https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html#tag-conventions

Why is this important?

• Customers want to use custom tagging for access controls, chargeback/showback.

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>