Labels: Add acs-top-50 if the customer is on this list Top ACS and OPP
Customers and ACS Assign (1/6/2024)
https://docs.google.com/spreadsheets/d/1segRFEaBrmDWro4W41VCR5NW6oH73ZA96ypmfH-hho4/edit?gid=976816933#gid=976816933

Description:

Some of our ACS users would like to apply Gitops principles without using our CR  solution. That may be  because this method is not possible for them (as is the case for ACSCS) or they simply have different gitops tools that cannot benefit from the CR approach.

These users should be able to use ACS API directly instead of the Kube API.

Goal Summary:

ACSCS and other users, may apply gitops principles to manage ACS policies as code. Prominent gitops tool examples include

• Github actions
• Tekton tasks

Goals and expected user outcomes:

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona
https://docs.google.com/document/d/15Q9w7rL7Op59YN8FLaPbSuTHoTj2qsdc38_5B_9-gD8/edit#heading=h.2nhcl1in3nwh
and which existing features, if any, will be expanded. Complete during New
status.

<your text here>

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.

<enter general Feature acceptance here>

Success Criteria or KPIs measured:

A list of specific, measurable criteria that will be used to determine if
the feature is successful. Include key performance indicators (KPIs) or
other metrics., etc. Initial completion during Refinement status.

<enter success criteria and/or KPIs here>