[bitnami/argo-cd] Add native support for ConfigManagementPlugins #27628

maxnitze · 2024-07-02T11:07:25Z

Description of the change

Adding support for ArgoCD Config Management Plugins (CMP) to the chart.

Argo CD's "native" config management tools are Helm, Jsonnet, and Kustomize. If you want to use a different config management tools, or if Argo CD's native tool support does not include a feature you need, you might need to turn to a Config Management Plugin (CMP).

Adding those plugins creates a bit of overhead, as there are some volumes that need to be shared between the repo server and the sidecar container of the plugin and the sidecar configuration in general. This is automatically added when the plugins are enabled.

Benefits

ConfigManagementPlugins can be enabled directly from the chart.

Example with the argocd-vault-plugin

Here's an example of how I would be using it for a CMP that adds support for the argocd-vault-plugin.

repoServer:
  extraVolumes:
    - name: vault-configuration
      secret:
        secretName: argo-cd-vault-configuration

  configManagementPlugins:
    enabled: true
    additionalBinaries:
      - name: argocd-vault-plugin
        url: https://github.com/argoproj-labs/argocd-vault-plugin/releases/download/v1.18.1/argocd-vault-plugin_1.18.1_linux_amd64
    plugins:
      - name: avp-helm
        spec:
          init:
            command:
              - /bin/sh
              - -c
              - |
                #!/usr/bin/env bash
                set -Eeuo pipefail
                
                # add all repositories from dependencies of this chart
                for REPO_URL in $(helm dependency list | tail -n+2 | tr -s '[:space:]' | cut -f3)
                do
                  # skip entries that reference local charts
                  if [[ "${REPO_URL}" == file://* ]]; then continue; fi
                  helm repo add $(echo -n "${REPO_URL}" | base64 -w0) "${REPO_URL}"
                done
                
                # finally download the charts dependencies
                helm dependency build
          generate:
            command:
              - /bin/sh
              - -c
              - |
                #!/usr/bin/env bash
                set -Eeuo pipefail
                
                # do some magic with the parameters
                # see https://github.com/argoproj-labs/argocd-vault-plugin/issues/566 for an example
                
                helm template ${HELM_RELEASE_NAME} \
                  --namespace ${ARGOCD_APP_NAMESPACE} \
                  ${HELM_VALUE_FILES} \
                  ${HELM_PARAMETERS} \
                  ${HELM_EXTRA_PARAMETERS} \
                  ./ |
                argocd-vault-plugin generate - -c /run/secrets/vault-configuration/config.yaml
          allowConcurrency: true
          lockRepo: false
        sidecar:
          image:
            repository: alpine/helm
            tag: 3.12.3
          extraEnvVars:
            # root filesystem is read-only, so we need to move the Helm home folders to /tmp
            - name: HELM_CACHE_HOME
              value: /tmp/helm/cache
            - name: HELM_CONFIG_HOME
              value: /tmp/helm/config
            - name: HELM_DATA_HOME
              value: /tmp/helm/data
          extraVolumeMounts:
            - mountPath: /run/secrets/vault-configuration/config.yaml
              name: vault-configuration
              subPath: config.yaml

Possible drawbacks

The change tries to make everything as much configurable as possible. So no drawbacks there (hopefully).

The change in general is opt-in. So no undesired changes to existing installations.

Applicable issues

None

Additional information

`argocd.tplvalues.merge-with-precedence` Helper

I introduced a new helper for merging values from a list with precedence to later entries.

This was necessary, because the helper common.tplvalues.merge has one major "flaw", that I needed fixed here:

context1:
  enabled: true
  name: 1001
  isRunning: true
context2:
  enabled: false
  name: 1234
  isRunning: false

When I merge these two with include "common.tplvalues.merge" (dict "values" (list .context1 .context2) "context" $), the result is

mergedContext:
  enabled: true
  name: 1234
  isRunning: true

I don't know if this is a bug or a feature (the comment of the helper says, that "precedence is consistent with http://masterminds.github.io/sprig/dicts.html#merge-mustmerge").

Since I was merging container security contexts here, I wanted to be give the option to deactivate the readOnlyRootFilesystem, for example. Or disable the context completely.

The result when using the new helper include "argocd.tplvalues.merge-with-precedence" (dict "values" (list .context1 .context2) "context" $) is

mergedContext:
  enabled: false
  name: 1234
  isRunning: false

Checklist

Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
All commits signed off and in agreement of Developer Certificate of Origin (DCO)

maxnitze · 2024-07-15T14:39:34Z

Not sure why the VIB Verify check failed here. But it also failed for other PRs. Maybe somethings wrong with the action?

andresbono

Thank you very much for your contribution, this could be a great addition! I left some initial questions. Let's discuss them before we go more in depth!

andresbono · 2024-07-18T09:02:37Z

bitnami/argo-cd/values.yaml

+    ## @param repoServer.configManagementPlugins.enabled Whether the config management plugins are enabled or not.
+    enabled: false


Is this new value repoServer.configManagementPlugins.enabled actually needed? Wouldn't it be enough to check if repoServer.configManagementPlugins.plugins has elements or not?

If it has elements, then we consider the feature activated

Otherwise, deactivated

We could, yeah. This is the pattern we use for most features though, right? I also like the fact, that for debugging purposes you can just disable it here without having to delete the whole plugins config.

andresbono · 2024-07-18T09:35:58Z

bitnami/argo-cd/values.yaml

+    ##   - name: my-custom-binary
+    ##     url: https://www.example.com/my-custom-binary-1.2.3
+    ##     customScript: ""
+    additionalBinaries: []


Could we achieve the same by using repoServer.initContainers? And it gives you more flexibility... In addition to that, I would expect that users also customize their container images to include any required binaries baked in the image instead of having to download the binaries every time at runtime. Does it make sense?

Yep. In the end having the binaries here will only fill an init container. You can still use your own init container or bake your binaries into your custom image. You just have to make sure, that the binaries are on the path in the sidecar container, that runs your plugin.

The whole point of the change was to get rid of the boilerplate and having a simple way of configuring a CMP. That why I included this. But as stated, this is fully optional.

While I was thinking about it: Maybe we can skip the "customScript" part and recommend to use an own init container or custom image in that case. But for the easy cases, where the binary can just be downloaded from a given URL, I would prefre to keep the functionality.

Yes, at the very least, we should skip the customScript part. Will you update the PR? Once we have that removed, let's see if it makes sense to keep simplifying the implementation. Thanks!

maxnitze · 2024-07-31T14:17:47Z

Updated the chart and removed the custom script option of the additional binaries.

andresbono · 2024-08-08T13:11:38Z

@maxnitze, thank you for addressing this. Let me take a look at the changes to get back to you. No worries about the conflicts, I'll take care of resolving them.

andresbono · 2024-08-14T13:03:54Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+              name: cmp-additional-binaries
+        {{- if .Values.repoServer.configManagementPlugins.additionalBinaries }}
+        - name: download-additional-binaries
+          image: {{ include "common.images.image" (dict "imageRoot" (dict "repository" "curlimages/curl" "tag" "latest") "global" .Values.global) }}


Any container image should be maintained by Bitnami and configured in a standard way from values.yaml. You could use bitnami/os-shell. Look at the volumePermissions.image value to follow a similar pattern.

Do you have any concerns with that?

No issues at all! I remember thinking about this when I added the init-container. I think I just forgot about it. Anyway, added it now!

andresbono

Hi, I just added some comments to the PR. Could you please check? Thank you!

andresbono · 2024-09-02T10:42:59Z

bitnami/argo-cd/templates/_helpers.tpl

@@ -191,6 +191,24 @@ Create the name of the service account to use for Dex
 {{- end -}}
 {{- end -}}

+{{/*


I'm not sure what is the value of having this helper function here in argo-cd. It looks like a generic function unrelated to argo-cd itself.

This should go in the common library, although I would try to avoid adding more complexity and try to avoid the usage of this helper if possible.

Yep, I would really like to move this to the common chart. I posted my reasoning to the description of the PR. But here's the condensed version of it:

Let's assume we have these two dicts:

context1: enabled: true name: 1001 isRunning: true someOtherKey: "someOtherValue" context2: enabled: false name: 1234 isRunning: false anotherKey: "anotherValue"

When we merge both with common.tplvalues.merge (from the common chart), the resulting dict is

mergedContext: enabled: true name: 1234 isRunning: true someOtherKey: "someOtherValue" anotherKey: "anotherValue"

So even though we would assume the values from context2 to have precedence (which they have for name, for example), the boolean values stay the same.

In general it is not possible to overwrite any keys from context1 with values that are falsy.

I'm not sure if this is a bug or by design (the docs say that "precedence is consistent with http://masterminds.github.io/sprig/dicts.html#merge-mustmerge"). This helper here is designed to circumvent that.

To be implemented in common, see #29668

andresbono · 2024-09-02T10:43:51Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+            - /opt/bitnami/argo-cd/bin/argocd
+            - /additional-binaries/argocd-cmp-server
+          {{- if .Values.repoServer.containerSecurityContext.enabled }}
+          securityContext: {{- omit .Values.repoServer.containerSecurityContext "enabled" | toYaml | nindent 12 }}


Suggested change

securityContext: {{- omit .Values.repoServer.containerSecurityContext "enabled" | toYaml | nindent 12 }}

securityContext: {{- include "common.compatibility.renderSecurityContext" (dict "secContext" .Values.repoServer.containerSecurityContext "context" $) | nindent 12 }}

andresbono · 2024-09-02T10:51:44Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+        {{- with .Values.repoServer.configManagementPlugins.additionalBinaries }}
+        {{- if .binaries }}
+        - name: download-additional-binaries
+          image: {{ include "common.images.image" (dict "imageRoot" .image "global" $.Values.global) }}


This should go into its own helper function (see examples for the other images):

{{/* Return the proper CMP binary downloader image name */}} {{- define "argocd.repoServer.configManagementPlugins.additionalBinaries.image" -}} {{- include "common.images.image" ( dict "imageRoot" .Values.repoServer.configManagementPlugins.additionalBinaries.image "global" .Values.global ) -}} {{- end -}}

and be called like:

Suggested change

image: {{ include "common.images.image" (dict "imageRoot" .image "global" $.Values.global) }}

image: {{ include "argocd.repoServer.configManagementPlugins.additionalBinaries.image" . }}

andresbono · 2024-09-02T10:52:27Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+          imagePullPolicy: {{ .image.pullPolicy }}
+          command:
+            - sh
+            - -c


Should we pass the -ec flags to detect errors?

andresbono · 2024-09-02T11:00:44Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+        - name: {{ $plugin.name }}
+          image: {{ include "common.images.image" (dict "imageRoot" $plugin.sidecar.image "global" $.Values.global) }}


I think it would be better to simplify all this and let users decide what will be the sidecar preferred structure. It simplify our maintenance at the same time it allows total flexibility for users.

It would be the same approach that we follow in .Values.repoServer.sidecars for example.

This block is kind of the whole point of this PR. There are some mounts that have to be mounted to specific directories, like the CMP binary, the plugins folder or the plugin.yml.

The user still has the option to completely set it by him or herself (through .Values.repoServer.sidecars). But removing this opinionated block defeats the whole purpose of this PR.

The thing is... This assumes a very specific object structure for each element in the plugins array.
The main value the PR adds is automating the volumeMounts that are required for the sidecars to work. Could we sth like this instead?

{{- range $sidecar := .Values.repoServer.configManagementPlugins.sidecars }} {{- include "common.tplvalues.render" (dict "value" $sidecar "context" $) | nindent 8 }} volumeMounts: - name: cmp-{{ $sidecar.name }} mountPath: /home/argocd/cmp-server/config/plugin.yaml subPath: plugin.yaml - name: cmp-server-plugins mountPath: /home/argocd/cmp-server/plugins - name: cmp-additional-binaries mountPath: {{ $additionalBinariesDir }} - name: cmp-server-tmp-dir mountPath: /tmp {{- end }}

This way, we help users setting up mounted directories while we keep flexible enough for users to customize the sidecars.

andresbono · 2024-09-02T11:02:03Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+            {{- end }}
+          {{- if $plugin.sidecar.resources }}
+          resources: {{- toYaml $plugin.sidecar.resources | nindent 12 }}
+          {{- else if and $plugin.sidecar.resourcePreset (ne $plugin.sidecar.resourcesPreset "none") }}


There is a typo here, but in any case, refer to my previous comment about simplifying all this code and allow users to set their sidecars config explicitly.

Suggested change

{{- else if and $plugin.sidecar.resourcePreset (ne $plugin.sidecar.resourcesPreset "none") }}

{{- else if and $plugin.sidecar.resourcesPreset (ne $plugin.sidecar.resourcesPreset "none") }}

andresbono · 2024-09-02T11:03:02Z

bitnami/argo-cd/values.yaml

+        ## pullSecrets:
+        ##   - myRegistryKeySecretName
+        ##
+        pullSecrets: [ ]


Should this image be added to argocd.imagePullSecrets?

github-actions · 2024-09-18T01:27:25Z

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

Signed-off-by: Max Nitze <[email protected]>

…a custom script Signed-off-by: Max Nitze <[email protected]>

…inaries in config management plugins Signed-off-by: Max Nitze <[email protected]>

…ix typos Signed-off-by: Max Nitze <[email protected]>

maxnitze · 2024-09-20T15:18:27Z

I'm back from a longer vacation and looked through your remarks. Had some comments myself, but fixed most of them.

On the argocd.tplvalues.merge-with-precedence helper topic, should I create a PR in the common chart and update this afterwards? Or would it be okay to keep it as is and create the PR in the common chart afterwards (I guess there will be some discussion, if that is a valid case for the common chart or not).

Signed-off-by: Bitnami Containers <[email protected]>

andresbono · 2024-09-23T08:00:32Z

On the argocd.tplvalues.merge-with-precedence helper topic, should I create a PR in the common chart and update this afterwards?

Yes, please. Let's do it like that. Once the new PR for the bitnami/common library is merged, we can continue with the final changes here.

Thank you!

maxnitze · 2024-09-23T09:13:14Z

Created #29566 to discuss what the correct fix for the issue is. Will come back here once that issue is closed.

andresbono · 2024-09-30T06:27:43Z

Created #29566 to discuss what the correct fix for the issue is. Will come back here once that issue is closed.

Thank you, @maxnitze. I commented on the new issue. Your suggestion for the new helper will be a good addition for bitnami/common.

Signed-off-by: Bitnami Containers <[email protected]>

juan131 · 2024-10-02T08:56:16Z

bitnami/argo-cd/templates/_helpers.tpl

@@ -191,6 +191,24 @@ Create the name of the service account to use for Dex
 {{- end -}}
 {{- end -}}

+{{/*


To be implemented in common, see #29668

juan131 · 2024-10-02T09:07:29Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+        - name: copy-cmp-server-binary
+          image: {{ include "argocd.image" . }}
+          imagePullPolicy: {{ .Values.image.pullPolicy }}
+          command:
+            - /bin/cp
+            - -n
+            - /opt/bitnami/argo-cd/bin/argocd
+            - /additional-binaries/argocd-cmp-server
+          {{- if .Values.repoServer.containerSecurityContext.enabled }}
+          securityContext: {{- include "common.compatibility.renderSecurityContext" (dict "secContext" .Values.repoServer.containerSecurityContext "context" $) | nindent 12 }}
+          {{- end }}
+          volumeMounts:
+            - mountPath: /additional-binaries
+              name: cmp-additional-binaries
+        {{- with .Values.repoServer.configManagementPlugins.additionalBinaries }}
+        {{- if .binaries }}
+        - name: download-additional-binaries
+          image: {{ include "argocd.repo-server.config-management-plugins.additional-binaries.image" $ }}
+          imagePullPolicy: {{ .image.pullPolicy }}
+          command:
+            - sh
+            - -ec
+          args:
+            - |-
+              {{- range $additionalBinary := .binaries }}
+              # downloading {{ $additionalBinary.name }}
+              curl -L {{ $additionalBinary.url }} -o /additional-binaries/{{ $additionalBinary.name }}
+              chmod +x /additional-binaries/{{ $additionalBinary.name }}
+              {{- end }}
+          volumeMounts:
+            - mountPath: /additional-binaries
+              name: cmp-additional-binaries


These two steps look overcomplicated to me. I guess we're using bitnami/os-shell to download extra binaries because bitnami/argo-cd lacks curl, right?

juan131 · 2024-10-02T09:10:09Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+          {{- if $plugin.sidecar.customCommand }}
+          command: {{- include "common.tplvalues.render" (dict "value" $plugin.sidecar.customCommand "context" $) | nindent 12 }}
+          {{- else }}
+          command:
+            - {{ $additionalBinariesDir }}/argocd-cmp-server
+          {{- end }}
+          {{- if $plugin.sidecar.customArgs }}
+          args: {{- include "common.tplvalues.render" (dict "value" $plugin.sidecar.customArgs "context" $) | nindent 12 }}
+          {{- end }}


We always use xxx.command and xxx.args as paramaters name for users to customize their custom command/args. For consistency with the catalog, please use this naming.

juan131 · 2024-10-02T09:35:58Z

bitnami/argo-cd/templates/repo-server/deployment.yaml

+        - name: {{ $plugin.name }}
+          image: {{ include "common.images.image" (dict "imageRoot" $plugin.sidecar.image "global" $.Values.global) }}


The thing is... This assumes a very specific object structure for each element in the plugins array.
The main value the PR adds is automating the volumeMounts that are required for the sidecars to work. Could we sth like this instead?

{{- range $sidecar := .Values.repoServer.configManagementPlugins.sidecars }} {{- include "common.tplvalues.render" (dict "value" $sidecar "context" $) | nindent 8 }} volumeMounts: - name: cmp-{{ $sidecar.name }} mountPath: /home/argocd/cmp-server/config/plugin.yaml subPath: plugin.yaml - name: cmp-server-plugins mountPath: /home/argocd/cmp-server/plugins - name: cmp-additional-binaries mountPath: {{ $additionalBinariesDir }} - name: cmp-server-tmp-dir mountPath: /tmp {{- end }}

This way, we help users setting up mounted directories while we keep flexible enough for users to customize the sidecars.

juan131 · 2025-02-25T08:27:14Z

Closing due to lack of activity, feel free to reopen it if the work is resumed.

maxnitze · 2025-02-25T08:49:57Z

Still have it on my TODO list. Sorry for that. Will re-open once I find the time to do it!

github-actions bot added argo-cd triage Triage is needed labels Jul 2, 2024

github-actions bot assigned carrodher Jul 2, 2024

github-actions bot requested a review from carrodher July 2, 2024 11:07

maxnitze force-pushed the feature/argocd-custom-management-plugin-support branch from 1d02ec8 to 8e0232a Compare July 2, 2024 11:10

carrodher added verify Execute verification workflow for these changes in-progress labels Jul 2, 2024

github-actions bot removed the triage Triage is needed label Jul 2, 2024

github-actions bot unassigned carrodher Jul 2, 2024

github-actions bot removed the request for review from carrodher July 2, 2024 19:19

github-actions bot assigned andresbono Jul 2, 2024

github-actions bot requested a review from andresbono July 2, 2024 19:19

maxnitze force-pushed the feature/argocd-custom-management-plugin-support branch 5 times, most recently from 255d610 to 3801362 Compare July 9, 2024 09:54

maxnitze force-pushed the feature/argocd-custom-management-plugin-support branch from 08f19c9 to ad57930 Compare July 15, 2024 14:24

maxnitze force-pushed the feature/argocd-custom-management-plugin-support branch from a74cb4f to 349c29d Compare July 16, 2024 12:42

andresbono reviewed Jul 18, 2024

View reviewed changes

maxnitze force-pushed the feature/argocd-custom-management-plugin-support branch 2 times, most recently from 8dcbbb4 to 7f95571 Compare July 23, 2024 15:57

maxnitze force-pushed the feature/argocd-custom-management-plugin-support branch from 09b9eae to 6107d31 Compare July 31, 2024 14:17

andresbono reviewed Aug 14, 2024

View reviewed changes

maxnitze force-pushed the feature/argocd-custom-management-plugin-support branch from 6ea59ed to ff3d0f6 Compare August 20, 2024 14:03

andresbono reviewed Sep 2, 2024

View reviewed changes

github-actions bot added the stale 15 days without activity label Sep 18, 2024

Max Nitze added 4 commits September 20, 2024 16:35

[bitnami/argo-cd] Add native support for ConfigManagementPlugins

8f06ff2

Signed-off-by: Max Nitze <[email protected]>

[bitnami/argo-cd] Remove option to download additional binaries with …

3920fd5

…a custom script Signed-off-by: Max Nitze <[email protected]>

[bitnami/argo-cd] Use bitnami/os-shell image to download additional b…

f000ab8

…inaries in config management plugins Signed-off-by: Max Nitze <[email protected]>

[bitnami/argo-cd] Use common helpers to render security context and f…

99fa136

…ix typos Signed-off-by: Max Nitze <[email protected]>

maxnitze force-pushed the feature/argocd-custom-management-plugin-support branch from 0fedbce to 99fa136 Compare September 20, 2024 15:16

Update CHANGELOG.md

fd6d969

Signed-off-by: Bitnami Containers <[email protected]>

github-actions bot removed the stale 15 days without activity label Sep 21, 2024

maxnitze mentioned this pull request Sep 23, 2024

[bitnami/common] common.tplvalues.merge ignores precedence on falsy values #29566

Closed

maxnitze mentioned this pull request Sep 30, 2024

[bitnami/common] Add common.tplvalues.merge-overwrite helper #29668

Merged

4 tasks

carrodher requested a review from juan131 October 1, 2024 16:03

carrodher assigned juan131 and unassigned andresbono Oct 1, 2024

juan131 added the on-hold Issues or Pull Requests with this label will never be considered stale label Oct 2, 2024

Update CHANGELOG.md

ee1bedb

Signed-off-by: Bitnami Containers <[email protected]>

github-actions bot removed the in-progress label Oct 2, 2024

juan131 requested changes Oct 2, 2024

View reviewed changes

juan131 closed this Feb 25, 2025

juan131 removed the on-hold Issues or Pull Requests with this label will never be considered stale label Feb 25, 2025

github-actions bot added the solved label Feb 25, 2025

		## @param repoServer.configManagementPlugins.enabled Whether the config management plugins are enabled or not.
		enabled: false

	securityContext: {{- omit .Values.repoServer.containerSecurityContext "enabled" \| toYaml \| nindent 12 }}
	securityContext: {{- include "common.compatibility.renderSecurityContext" (dict "secContext" .Values.repoServer.containerSecurityContext "context" $) \| nindent 12 }}

	image: {{ include "common.images.image" (dict "imageRoot" .image "global" $.Values.global) }}
	image: {{ include "argocd.repoServer.configManagementPlugins.additionalBinaries.image" . }}

		- name: {{ $plugin.name }}
		image: {{ include "common.images.image" (dict "imageRoot" $plugin.sidecar.image "global" $.Values.global) }}

	{{- else if and $plugin.sidecar.resourcePreset (ne $plugin.sidecar.resourcesPreset "none") }}
	{{- else if and $plugin.sidecar.resourcesPreset (ne $plugin.sidecar.resourcesPreset "none") }}

[bitnami/argo-cd] Add native support for ConfigManagementPlugins #27628

[bitnami/argo-cd] Add native support for ConfigManagementPlugins #27628

Conversation

maxnitze commented Jul 2, 2024

Description of the change

Benefits

Example with the argocd-vault-plugin

Possible drawbacks

Applicable issues

Additional information

argocd.tplvalues.merge-with-precedence Helper

Checklist

maxnitze commented Jul 15, 2024

andresbono left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

maxnitze commented Jul 31, 2024 • edited Loading

andresbono commented Aug 8, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

andresbono left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

github-actions bot commented Sep 18, 2024

maxnitze commented Sep 20, 2024

andresbono commented Sep 23, 2024 • edited Loading

maxnitze commented Sep 23, 2024

andresbono commented Sep 30, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

juan131 commented Feb 25, 2025

maxnitze commented Feb 25, 2025

`argocd.tplvalues.merge-with-precedence` Helper

maxnitze commented Jul 31, 2024 •

edited

Loading

andresbono commented Sep 23, 2024 •

edited

Loading