Weirdness in preprocessors about argocd-lovely-plugin HOT 3 CLOSED

I got it working with:

  source:
    path: deploy
    plugin:
      env:
      - name: LOVELY_PREPROCESSORS
        value: sed -i 's/<<environment>>/dev-lovely/g' values.yaml || true

Seems preprocessors run per directory in deploy folder. I suppose this is intentional, however it might be good to mention in documentation.

from argocd-lovely-plugin.

Ok, yes, good call. The individual parts of a composite application are treated completely independently.

This isn't actually great as you see, because one of the folders won't have a values.yaml, and the other does, so you need to skip all error handling.

This needs a think about and redesign to make it more friendly.

from argocd-lovely-plugin.

I have added the ability to configure preprocessors and plugins on a per sub-application basis. For your example try this:

  source:
    path: deploy
    plugin:
      env:
      - name: LOVELY_PREPROCESSORS_YAML
        value: |-
          magento:
          - "sed -i 's/<<environment>>/dev-lovely/g' values.yaml"
      name: argocd-lovely-plugin

from argocd-lovely-plugin.