Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pass helm values from separate repo #60

Open
chanakya-svt opened this issue Jun 4, 2024 · 1 comment
Open

Pass helm values from separate repo #60

chanakya-svt opened this issue Jun 4, 2024 · 1 comment

Comments

@chanakya-svt
Copy link

chanakya-svt commented Jun 4, 2024

Having trouble passing the helm values from one repository to another.

I have the following helmfile.yaml in some-repo-a

bases:
  - ../../../bases/helm-defaults.yaml
missingFileHandler: Error
releases:
  - name: "namespaces"
    namespace: "default"
    createNamespace: true
    chart: "../../../charts/namespaces"
    values:
      - {{ env "ARGOCD_ENV_NAMESPACES_VALUES_FILE" | quote }}

I have the following ArgoCD Application config in some-repo-b

spec:
      project: default
      sources:
        - repoURL: "https://github.com/some-repo-a"
          path: "src"
          targetRevision: "main"
          plugin:
            name: "helmfile"
            env:
              - name: "NAMESPACES_VALUES_FILE"
                value: $values/path/to/values.yaml
        - repoURL: "https://github.com/some-repo-b"
          targetRevision: main
          ref: values
     destination:
        server: "in-cluster"
        namespace: "default"

I configured the ArgoCD RepoServer following this guide

When I try to sync the application I am getting /path/to/values.yaml file or directory does not exists.

Is there a way to pass the values yaml from a different repository like the above setup.

ArgoCD version: v2.11.2
argo-cd-helmfile: v0.3.11
helmfile: v0.165.0

Thank you

@chanakya-svt
Copy link
Author

@travisghansen any insights on this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant