This PR proposes a set of conventions for organizing Assemble platform components into a single root ArgoCD application.
Currently, there is only one platform component (openshift-pipelines-operator) besides ArgoCD itself which must be provisioned first and cannot be part of the root application.
As new platform components are added, Helm charts can be added to the charts/ directory and referenced by ArgoCD Applications in the applications/.
Applications in the applications/ directory are automatically included by the root ArgoCD application located in the root directory of the repository.
Upcoming planned platform components that could be included as soon as charts are ready:
Backstage
Keycloak
Postgres
See provisioning instructions included in the README to understand the provisioning steps from a user's perspective.
This PR proposes a set of conventions for organizing Assemble platform components into a single root ArgoCD application.
charts/directory and referenced by ArgoCD Applications in theapplications/.applications/directory are automatically included by the root ArgoCD application located in the root directory of the repository.Upcoming planned platform components that could be included as soon as charts are ready:
See provisioning instructions included in the README to understand the provisioning steps from a user's perspective.