⚠ MAAS Terraform Provider ownership changed

News
1

Hey MAAS Users, Hackers and Fans!

The Terraform Provider for MAAS repository is moving under the Canonical GitHub organisation with a new name github.com/canonical/terraform-provider-maas.

Because of this change you might be warned about new module name:

❯ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding maas/maas versions matching "2.2.0"...
- Installing maas/maas v2.2.0...
- Installed maas/maas v2.2.0 (self-signed, key ID A7209377EEEC4607)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

╷
│ Warning: Additional provider information from registry
│
│ The remote registry returned warnings for registry.terraform.io/maas/maas:
│ - For users on Terraform 0.13 or greater, this provider has moved to canonical/maas. Please update your source in required_providers.
╵

Ensure you are pointing at the new provider name inside your Terraform module(s), which is canonical/maas:

  1. Manually update the list of required providers in your Terraform module(s):

    terraform {
  required_providers {
    maas = {
-     source  = "maas/maas"
+     source  = "canonical/maas"
      version = "~>2.0"
    }
  }
}

  2. Upgrade your provider dependencies to add the canonical/maas provider info:

    terraform init -upgrade

  3. Replace the provider reference in your state:

    terraform state replace-provider maas/maas canonical/maas

  4. Upgrade your provider dependencies to remove the maas/maas provider info:

    terraform init -upgrade

References:

1 Like