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_release does not allow https or oci for azure container registry #31897

Closed
vikrantoct7 opened this issue Sep 29, 2022 · 2 comments
Closed
Labels
bug new new issue not yet triaged provider/helm

Comments

@vikrantoct7
Copy link

Terraform Version

Terraform v1.2.2 on linux_amd64

Terraform Configuration Files

NA

Debug Output

Could not download chart: looks like https://pocacringress.azurecr.io/helm/ is not valid chart repository or cannot reached: failed to fetch https://pocacringress.azurecr.io/helm//index.yaml: 404

Expected Behavior

Chart should be fetch. helm pull oci://pocacringress.azurecr.io/helm/ --version --untar worked well

Actual Behavior

Could not download chart: looks like https://pocacringress.azurecr.io/helm/ is not valid chart repository or cannot reached: failed to fetch https://pocacringress.azurecr.io/helm//index.yaml: 404

Steps to Reproduce

terraform init
terraform apply --auto-approve

Additional Context

Chart name is "hello-world". code sample is here

Install Nginx Ingress using Helm Chart

resource "helm_release" "hello-world" {
name = "hello-world"
chart = "hello-world"
namespace = "hello-world"
create_namespace = "true"
repository = "https://pocacringress.azurecr.io/helm/hello-world"
version = "0.1.0"
wait = "true"
force_update = "true"

}

References

https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release

hashicorp/terraform-provider-helm#765

@vikrantoct7 vikrantoct7 added bug new new issue not yet triaged labels Sep 29, 2022
@vikrantoct7
Copy link
Author

this is reported under terraform-provider-helm repo

@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2022

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 Nov 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug new new issue not yet triaged provider/helm
Projects
None yet
Development

No branches or pull requests

2 participants