Epic Goal

There are customers and team like validated pattern who are using helm to deploy policies. Currently they cannot use PolicyGenerator

Implement Helm based support for PolicyGenerator similar to: https://github.com/eformat/acm-gitops-helm

Why is this important?

... customer using Helm to deploy Policies, this is also used by ValidatedPattern team. they cannot use PolicyGenerator

Scenarios

...

Acceptance Criteria

... Security concerns are clarified and addressed

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>