v1.0.0

Note

This release is identical to the cloudfoundry-community release version v0.53.1
Instructions for switching to the philips-labs hosted version of the cloud foundry provider are below

Switching to philips-labs/cloudfoundry

Switching your project to the philips-labs/cloudfoundry provider can be done by following these steps

Step 1. Modify the Terraform version reference configuration

Update your Terraform scripts so they point to this provider:

terraform {
 required_providers {
   cloudfoundry = {
-      source  = "cloudfoundry-community/cloudfoundry"
-      version = ">= 0.53.1"
+      source  = "philips-labs/cloudfoundry"
+      version = ">= 1.0.0"
   }
  }
}

Step 2. Update your Terraform state

Terraform state is tied to a specific provider as well, so the reference must be updated. This can be done by executing the following Terraform command:

terraform state replace-provider cloudfoundry-community/cloudfoundry philips-labs/cloudfoundry

Note

Under some conditions you may need to run terraform init before the above command. You might encounter errors downloading the community provider, however your backend should still have been initialized OK. This should allow you to execute the state replace-provider command.

Step 3. Update and check provider reference

Update and verify there are no references left to the community provider:

terraform init
terraform providers

Important

Published Provider releases on this repository will have the following signature notification

(self-signed, key ID C0E4EB79E9E6A23D)

The terraform providers command should output something like:

Providers required by configuration:
.
├── provider[registry.terraform.io/philips-labs/cloudfoundry] >= 1.0.0
└── provider[registry.terraform.io/philips-software/hsdp] >= 0.42.1

Providers required by state:

    provider[registry.terraform.io/philips-labs/cloudfoundry]

    provider[registry.terraform.io/philips-software/hsdp]

Note

Terraform modules you consume which have a dependency on the cloudfoundry-community/cloudfoundry provider should be updated accordingly. Please contact the maintainers of those modules for assistance. Alternatively, fork the modules.