-
Notifications
You must be signed in to change notification settings - Fork 37
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
Credential name doesn't work since 0.9.0 #310
Comments
@gboutry can you please point to where |
@gboutry my understanding is that sunbeam hardcodes the version of the terraform provider used by pulling it into the snap, please confirm. |
At snap build time, snapcraft will pull the providers respecting the plans' constraints. We don't set upper constraints on terraform provider and 0.9.0 got pulled in our latest edge. |
This job failed because credentials Error message:
|
sunbeam-terraform fails with new versions of juju terraform provider, see [1]. Pin the version to 0.8.0 until [1] is fixed and released. [1] juju/terraform-provider-juju#310 (cherry picked from commit b4aef8e)
sunbeam-terraform fails with new versions of juju terraform provider, see [1]. Pin the version to 0.8.0 until [1] is fixed and released. [1] juju/terraform-provider-juju#310 (cherry picked from commit 8231ca1)
Description
juju_model resource is breaking with value
sunbeam-microk8s-creds
(valid credentials registered in juju controller)Urgency
Blocker for our release
Terraform Juju Provider version
0.9.0
Terraform version
1.3.7
Terraform Configuration(s)
https://github.com/canonical/sunbeam-terraform/
Reproduce / Test
Create a machine controller Add a microk8s cloud to the controller Reference its credentials in sunbeam-terraform terraform init terraform apply
Debug/Panic Output
Notes & References
This is a regression introduced in
0.9.0
.Deploying with
0.8.0
works fine.The text was updated successfully, but these errors were encountered: