The Juju team is happy to announce that the Juju Terraform provider rc0.12.0 candidate is released on 23 April 2024!
Thanks to all the contributors including @aflynn50 @alesstimec @anvial @hmlanigan.
For specific dates for testing and release for the v.0.12.0, please refer to the 0.12.0 Release Planning post.
Note that because this is a release candidate, it’s not pushed onto the HashiCorp repository, so testing with the release candidate requires you to pull it and change the TF plan to use the local provider.
$ git checkout tags/rc0.12.0
$ make install
This will install the the provider in ~/.terraform.d/plugins/registry.terraform.io/juju/juju/0.12.0/linux_amd64
.
Update your configurations to use the local candidate:
terraform {
required_providers {
juju = {
source = "registry.terraform.io/juju/juju" # (uses local provider repository)
# source = "juju/juju" (uses the Hashicorp repository)
version = "=0.12.0"
}
}
}
LINKS:
NOTES:
- This release requires juju controller version 2.9.49 or later juju.
- This release uses juju client api code from the juju 3.5-beta1 candidate release.
- The added JAAS login enhancements requires Juju controller version 3.5.0 or higher.
- The added Juju secrets support requires Juju controller version 3.4.0 or higher.
ENHANCEMENTS:
- Support for user secret management is added. You can now use
juju_secret
andjuju_access_secret
resources to create and manage secrets, as well as grant/revoke access to the applications in your plan. You can also usejuju_secret
data source in your configuration to access a secret. - Provider config is enhanced with support for Client ID and secret to enable logging in to JAAS using client credentials.
BUG FIXES:
- Channel for charms in an application resource requires both track and risk (e.g.,
latest
vslatest/stable
). A validation for channel in application resource is added by @Aflynn50 in Validate channel in application resource by Aflynn50 · Pull Request #447 · juju/terraform-provider-juju · GitHub