search

GSA-TTS / terraform-cloudgov

Terraform modules for cloud.gov managed services
10 stars 2 forks source link

Update to new cloudfoundry provider #56

Open rahearn opened 2 weeks ago

rahearn commented 2 weeks ago

Story

As a devops engineer, I would like to use a better supported terraform provider for cloudfoundry, So that I can be confident that everything works properly and will continue to work as api v2 goes away

Solution

### Tasks
- [ ] Utilize https://registry.terraform.io/providers/cloudfoundry/cloudfoundry/latest/docs provider
- [ ] Determine if this is a breaking change and rev the semver appropriately

Acceptance Criteria

rahearn commented 2 weeks ago

more context/discussion: https://gsa-tts.slack.com/archives/C02U4Q9M5UH/p1729197775560979

rahearn commented 2 weeks ago

"breaking change" should be defined around both the parameters required for use of the modules as well as whether a resource created before the change can be cleanly managed by the provider after the change.

mogul commented 2 weeks ago

"breaking change" should be defined around both the parameters required for use of the modules as well as whether a resource created before the change can be cleanly managed by the provider after the change.

There's a lot of changes, and existing resources will have to be "orphaned" by removing them from the state, then re-importing them before the apply where the resource is updated to reference the new provider. The migration guide shows doing this with explicit terraform import CLI calls but I am pretty sure it could also be done with import blocks (which is probably better since the import and the reference to the new provider happen during the same apply).