You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, we manage a AppProject for each application we deploy. Often most of the info we need to create the AppProject is already in the app:
destination namespace
source helm chart
Other info is often consistent over various deployments but not currently tracked in *apps charts:
resource allow list (for cluster-wide stuff)
Describe the solution you'd like
We might benefit from (optionally) creating AppProjects directly in *-apps charts.
I'd l like to enable them individually for apps. Values to do so might look like so (example from first app in infra-apps):
argocd:
# Enable the Argo CD app deploymentname: argocd# current definition of "project" is a string for injection into the app and might need redefiningproject:
create: true# more appproject settings go here# ... snip
There are other possibilities to model the data, see below for a projects as top-level key approach.
Describe alternatives you've considered
Well, there is the status quo that i'm not happy with.
We could also create additional *-appproject charts but i'm wary of the additional maintenance burden for such a solution.
An alternative way to implement values would be like so:
argocd:
# Enable the Argo CD app deploymentname: argocd# keep current definition of project for appproject: "argo-cd"# ... snip# new top-level key containing all the apps.projects:
argocd:
create: true# name here would need to match `argocd.project` (or have some magick in the template to only grab it from there)name: "argo-cd"# more appproject settings go here
Affected chart
all *-app charts
Additional context
The argoconfigs has been ready for this for a while now, we just never got to implementing it.
Is your feature request related to a problem? Please describe.
Currently, we manage a AppProject for each application we deploy. Often most of the info we need to create the AppProject is already in the app:
Other info is often consistent over various deployments but not currently tracked in
*apps
charts:Describe the solution you'd like
We might benefit from (optionally) creating AppProjects directly in
*-apps
charts.I'd l like to enable them individually for apps. Values to do so might look like so (example from first app in infra-apps):
There are other possibilities to model the data, see below for a
projects
as top-level key approach.Describe alternatives you've considered
Well, there is the status quo that i'm not happy with.
We could also create additional
*-appproject
charts but i'm wary of the additional maintenance burden for such a solution.An alternative way to implement values would be like so:
Affected chart
*-app
chartsAdditional context
The
argoconfigs
has been ready for this for a while now, we just never got to implementing it.https://github.com/adfinis-sygroup/helm-charts/blob/b66006a29f2c9df27fd642bc94f9035a7ca5bb47/charts/argoconfig/templates/_appProject.yaml#L1-L17
The text was updated successfully, but these errors were encountered: