Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Provide customers the ability in OCM UI to to add AWS Tags to resources created with Machine Pool. 

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Complete during New status.

1. Allow customers to manage their cloud resources using custom-tags

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

1. Add AWS Tags when creating Machine Pool in an existing HCP cluster
2. View set AWS Tags when displaying the Machine Pool
3. Message(s) surfaced when the Create Machine Pool fails 
4. Support for OCM UI 
5. User supplied Tag keys and values are case sensitive.
6. Backend validations in place: 
   • Allow up to 25 Tags per Machine pool 
   • For each resource, each tag key must be unique, and each tag key can have only one value.

• • Tag do not begin with aws: which is reserved for AWS's usage
  • The tag key must be a minimum of 1 and a maximum of 128 Unicode characters in UTF-8.

• • The tag value must be a minimum of 0 and a maximum of 256 Unicode characters in UTF-8.

• • allowed characters are letters, numbers, spaces representable in UTF-8, and the following characters: _ . : / = + - @

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

1. HyperShift support: https://hypershift-docs.netlify.app/reference/api/#hypershift.openshift.io/v1beta1.AWSResourceTag 

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

1. Adding, Removing, or Updating AWS Tags on existing Machine Pools.

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

1. Create Machine pool page must be updated
2. It must be called out in the Note that updating tags on existing machine pools is not supported yet. 

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.