Cannot use file from other source as Helm --set-file param #13220
Labels
enhancement
New feature or request
multi-source-apps
Bugs or enhancements related to multi-source Applications.
Comments
|
@lucacox, multiple sources is not yet supported for Were you able to see the error if you reference value file from other source only, that is, only reference |
|
Supporting helm.fileParameters field under the multiple sources is very useful. I also have use case for and I noticed it is not supported. Is there a place where we can ask for features to be added? Or is this on your road map to be added? |
|
This PR would solve: #12508 |
10 tasks
|
I'm having the same issue. I'm using a centralized helm chart to deploy multiple ASP.NET services instead of replicating the same helm chart in many repos. I'm using the helm value extraDeploy this way: extraDeploy:
- |
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ include "aspnet-core.fullname" . }}-appsettings
labels: {{- include "common.labels.standard" . | nindent 6 }}
{{- if .Values.commonLabels }}
{{- include "common.tplvalues.render" ( dict "value" .Values.commonLabels "context" $ ) | nindent 6 }}
{{- end }}
{{- if .Values.commonAnnotations }}
annotations: {{- include "common.tplvalues.render" ( dict "value" .Values.commonAnnotations "context" $ ) | nindent 6 }}
{{- end }}
data:
appsettings.json: |-
{{- .Values.appsettings | nindent 4 }}So I need to set the helm value appsettings to the appsettings.json file content which is in my service configuration repo |
ishitasequeira
added
the
multi-source-apps
|
I found a workaround solution here: #3365 (comment) Basically you create an umbrella chart (like this one) in the same git repo where the |
ishitasequeira
added
enhancement
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 12, 2024
Added documentation for fileParameters in a helm source Application or the --helm-set-file cli option from argoproj#2751. Added a note about argoproj#13220 so users are aware. argoproj#12508 aims to remove this limitation so the warning can probably be removed with that.
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 12, 2024
Added documentation for fileParameters in a helm source Application or the --helm-set-file cli option from argoproj#2751. Added a note about argoproj#13220 so users are aware. argoproj#12508 aims to remove this limitation so the warning can probably be removed with that. Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
This was referenced Apr 12, 2024
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 17, 2024
Added documentation for fileParameters in a helm source Application or the --helm-set-file cli option from argoproj#2751. Added a note about argoproj#13220 so users are aware. argoproj#12508 aims to remove this limitation so the warning can probably be removed with that. Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 23, 2024
In multi-source applications helm values files can come from other repos if you use the ref syntax but it is not possible for the --set-file param to take files from other repos via the ref syntax. This extends the behavior to cover set-file parameters as well as the values files. fixes argoproj#13220, refs argoproj#17822 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
14 tasks
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 23, 2024
In multi-source applications helm values files can come from other repos if you use the ref syntax but it is not possible for the --set-file param to take files from other repos via the ref syntax. This extends the behavior to cover set-file parameters as well as the values files. fixes argoproj#13220, refs argoproj#17822 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
|
I created an implementation of this in #17941, hoping someone that's interested in this feature can help me get it over the finish line. |
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 25, 2024
Added documentation for fileParameters in a helm source Application or the --helm-set-file cli option from argoproj#2751. Added a note about argoproj#13220 so users are aware. argoproj#17941 aims to remove this limitation so the warning will be adjusted to mention the version that lands that support. Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 25, 2024
Added documentation for fileParameters in a helm source Application or the --helm-set-file cli option from argoproj#2751. Added a note about argoproj#13220 so users are aware. argoproj#17941 aims to remove this limitation so the warning will be adjusted to mention the version that lands that support. Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
crenshaw-dev
pushed a commit
that referenced
this issue
Apr 25, 2024
Added documentation for fileParameters in a helm source Application or the --helm-set-file cli option from #2751. Added a note about #13220 so users are aware. #17941 aims to remove this limitation so the warning will be adjusted to mention the version that lands that support. Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 27, 2024
In multi-source applications helm values files can come from other repos if you use the ref syntax but it is not possible for the --set-file param to take files from other repos via the ref syntax. This extends the behavior to cover set-file parameters as well as the values files. fixes argoproj#13220, refs argoproj#17822 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
Apr 27, 2024
In multi-source applications helm values files can come from other repos if you use the ref syntax but it is not possible for the --set-file param to take files from other repos via the ref syntax. This extends the behavior to cover set-file parameters as well as the values files. fixes argoproj#13220, refs argoproj#17822 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
May 4, 2024
In multi-source applications helm values files can come from other repos if you use the ref syntax but it is not possible for the --set-file param to take files from other repos via the ref syntax. This extends the behavior to cover set-file parameters as well as the values files. fixes argoproj#13220, refs argoproj#17822 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
May 4, 2024
In multi-source applications helm values files can come from other repos if you use the ref syntax but it is not possible for the --set-file param to take files from other repos via the ref syntax. This extends the behavior to cover set-file parameters as well as the values files. fixes argoproj#13220, refs argoproj#17822 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
cardoe
added a commit
to cardoe/argo-cd
that referenced
this issue
May 7, 2024
In multi-source applications helm values files can come from other repos if you use the ref syntax but it is not possible for the --set-file param to take files from other repos via the ref syntax. This extends the behavior to cover set-file parameters as well as the values files. fixes argoproj#13220, refs argoproj#17822 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist:
argocd version.Describe the bug
In Application using multiple sources reference of one source is not substituted in helm.fileParameters entries. It works (at least it seems) for the helm.valueFiles property
To Reproduce
Using this Application definition:
gives this error in the UI:
Notice this:
in
--valuesparam the$myRepois substituted with a.and in--set-filewith/tmp/47de275d-f0c3-419a-8382-9628f1674103/kratos.Expected behavior
The files in the gite repo should be used to set the variables in Helm
Screenshots
Version
The text was updated successfully, but these errors were encountered: