Upgrade the cf provider from cloudfoundry-community to cloudfoundry (V3) #967
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding CF URL for service_guid call
chore: update minimum recommended CF version
…#963) Bumps the pip group with 1 update in the /ci/test-space-egress directory: [h11](https://github.com/python-hyper/h11). Updates `h11` from 0.12.0 to 0.16.0 - [Commits](python-hyper/h11@v0.12.0...v0.16.0) --- updated-dependencies: - dependency-name: h11 dependency-version: 0.16.0 dependency-type: direct:production dependency-group: pip ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* update opensearch-ci-cf-read-only UAA client to have cloud_controller.global_auditor scope and authority * remove unnecessary scopes
Adding sandbox-bot-user to CF UAA
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this pull request:
This PR upgrades the terraform provider from the cloudfoundry-community version, which leverages v2 of the CF API, with the cloudfoundry version, that leverages V3 of the CF API.
This is a PR of the final state of the
.tffiles. This branch contains interim commits used to remove the old resources from the state file then import the resources under the new provider. After merging the PR, the branch will be manually restored and used to upgrade staging and production.The staging upgrade may require additional changes as the
test_cdnis not implemented in dev and therefore could not be tested.deploy-cf/terraform/stacks/cf/apps.tf
Line 2 in b0c3e4f
Additionally:
The upgrade process is not implemented as a concourse job or task. The provider versions do not have resource parity. The upgrade is achieved via a temporary script with a manual statefile intervention to deal with a non-importable resource. The script will be deleted after the upgrades are complete. https://github.com/cloud-gov/deploy-cf/blob/cf-provider-v3/terraform/scripts/update-provider.sh
Each environment will be updated individually. Production will be scheduled with the maintenance engineer.
This update should not result in any changes to the infrastructure (only terraform state).
The terraform plan and apply jobs in concourse are paused for each environment and will be unpaused when the state has been updated with no changes detected.
security considerations
None