Story (Required)

• This story will add a new component for argocd extension installer based on this repo - https://github.com/argoproj-labs/argocd-extension-installer/tree/main 
• The script that is run in this container will need changes to not use and EXTENSION_URL to download resources from the internet, instead it will make use of a file path or the compiled code for rollouts.

Background and Approach (Required)

• Argo Rollouts is tech preview in OpenShift GitOps and does not include any UI in the OpenShift Console. While longer term a dynamic plugin for the console is needed, a short term measure for providing a UI would be to enable the Rollouts extension in the Argo CD UI that GitOps already delivers.
• Follow steps for new delivery repository in comet - https://spaces.redhat.com/display/GITOPS/Adding+a+new+container+to+the+GitOps+Operator+bundle 
• Add the new product to the CPaaS repo here - https://gitlab.cee.redhat.com/cpaas-products/openshift-gitops
• Make additions to the upstream sources file and add the dockerfile to our midstream here - https://gitlab.cee.redhat.com/gitops-cpaas-midstream/gitops-midstream-repos
• Check the build process in Jenkins passes with no failures 

Out of Scope

• <Defines what is not included in this story.>

Dependencies

• <Describes what this story depends on. Dependent stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

• A new component in cpaas and midstream for the argocd-extension-installer
• Add it first in the nightly and then in 1.15 branch
• argocd-extension-installer component added to CPaaS pipeline for 1.15
• midstream managed gitops dis-gist folder added
• cgit/dist-git branch to create for manage gitops
• build successfully in midstream

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository/project.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.