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

Add pass-credentials option #847

Closed
toomai opened this issue Apr 6, 2022 · 2 comments
Closed

Add pass-credentials option #847

toomai opened this issue Apr 6, 2022 · 2 comments

Comments

@toomai
Copy link
Contributor

toomai commented Apr 6, 2022

Description

Helm cli offers a --pass-credentials flag to allow the client to pass credentials if the source of the chart archive in the index.yaml is coming from another source than the index.yaml.
It can be the case when the archives are hosted on a CDN.

I opened a MR with the change implemeted: #841

Potential Terraform Configuration

resource "helm_release" "gatekeeper" {
  namespace           = "gatekeeper"
  name                = "gatekeeper"
  repository          = "https://open-policy-agent.github.io/gatekeeper/charts"
  repository_username = "username"
  repository_password = "password"
  pass_credentials    = true
  chart               = "gatekeeper"
  version             = "v1.0.0"
}

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@toomai
Copy link
Contributor Author

toomai commented Apr 7, 2022

Is it possible the test fails due to a race condition ? I have a hard time finding the root cause of this. It's coming from terraform-exec
I can see it's tracked in hashicorp/terraform-exec#129. And given this issue, hashicorp/terraform-plugin-sdk#629, I think it's due to terraform-exec itself. On the other hand it's a concurrency test so maybe there something wrong in my code.
Could you maybe retry the job to see if it's a one-time thing ?

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants