Call for testing: The Juju Terraform provider v0.20.0-rc1

The Juju team is happy to announce that the Juju Terraform provider v0.20.0-rc1 candidate is released on 17 June 2025!

For specific dates for testing and release for the v0.20.0, please refer to the 0.20.0 Release Planning post.

This is a release candidate, it’s not yet 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/v0.20.0-rc1
 $ make install

This will install the the provider in ~/.terraform.d/plugins/registry.terraform.io/juju/juju/0.20.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.20.0"
    }
  }
}

LINKS:

NOTES:

  • This release requires Juju controller version 2.9.49 or higher Juju.
  • If using JAAS, this release requires Juju controller version 3.6.5 or higher.
  • This release uses Juju client api code from the Juju 3.6.4 release.

ENHANCEMENTS

  • BREAKING CHANGE to the juju_offer schema. The endpoint field is field has been removed in favor of the endpoints field, which allows for definition of multiple endpoints in a single juju application offer 752 by @SimoneDutto. This change requires a simple change to your existing plans: you need to change from endpoint: x to endpoints: [ x ] in juju_offer resources.
  • Introduction of juju_machine annotations 748 by @alesstimec.
  • Introduction of waiting for changes to take effect 738 by SimoneDutto, followed up by 738 that introduces a wait for application deletion and 760 that introduces a wait for integration deletion.
  • Removal of the juju_jaas_access_service_account resource 759 by @kian99. Service account authentication can now be used with JAAS to upload cloud credentials directly to the controller.

BUG FIXES

DOCUMENTATION

  • Introduction of auto-generated RTD documentation 758 by @SimoneDutto.
  • JAAS-related documentation improvements 746 by @tmihoc.

CI IMPROVEMENTS

  • Update to the acceptance test to upload cloud credentials to the controller at the start of test 737 by @kian99.
  • Allowing tests to diable waiting for changes to take effect 751 by @kian99.
1 Like