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

Helm error when specifying repo twice in args #1295

Closed
Tracked by #2847
clstokes opened this issue Sep 8, 2020 · 1 comment
Closed
Tracked by #2847

Helm error when specifying repo twice in args #1295

clstokes opened this issue Sep 8, 2020 · 1 comment
Assignees
Labels
area/helm kind/bug Some behavior is incorrect or out of spec mro2 Monica's list of 2st tier overlay related issues resolution/fixed This issue was fixed

Comments

@clstokes
Copy link

clstokes commented Sep 8, 2020

Problem description

Based on this user's experience with Pulumi's Helm Chart resource, it seems that specifying repo: ... in the top-level args object and in fetchOpts: { repo: ... } is problematic without great feedback to the user on why things fail.

Errors & Logs

Error: invocation of kubernetes:helm:template returned an error: failed to generate YAML for specified Helm chart: failed to pull chart: chart "argo/argo-cd" not found in https://argoproj.github.io/argo-helm repository

Reproducing the issue

const argocd = new kubernetes.helm.v3.Chart("argo", {
    repo: "argo", // removing this resolves the error
    chart: "argo-cd",
    fetchOpts: {
        repo: "https://argoproj.github.io/argo-helm",
    },
    namespace: argoNamespace.metadata.name,
}, {
    provider: kubernetesProvider,
    dependsOn: [argoNamespace]
})

Suggestions for a fix

Print an error or warning if both repo is specified in the top-level args object and in the fetchOpts block.

@mnlumi mnlumi added the mro2 Monica's list of 2st tier overlay related issues label Mar 28, 2023
@lblackstone lblackstone added the kind/bug Some behavior is incorrect or out of spec label Jul 14, 2023
@EronWright EronWright added the resolution/fixed This issue was fixed label May 14, 2024
@EronWright EronWright self-assigned this May 14, 2024
@EronWright
Copy link
Contributor

The upcoming Chart v4 resource has an input schema that is closer to Release, and doesn't have this same confusion. It has distinct options for installing a repository chart with or without a local repository alias.

I'm closing this as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm kind/bug Some behavior is incorrect or out of spec mro2 Monica's list of 2st tier overlay related issues resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

5 participants