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.
Summary
The Cloud.gov v2 API for Cloud Foundry is reaching its end-of-life. CF CLI versions 6 and 7 still rely on Cloud Foundry API v2 and will no longer work at some point with foundations that have disabled it. However, CF CLI v8 no longer uses Cloud Foundry API v2. For more details, refer to this link.
circleci/config.yml, is upgraded to CF CLI v8.9.0. This version supports Cloud Foundry API v3. Deploying to a cloud.gov space should work smoothly with this update
Update node/npm combo to fix the node/npm inconsistencies in circleci. node v22.1.0 uses nvm 10.7.0.
fec-pattern-library repo is also upgraded to use node v22.1.0 and nvm 10.7.0.
Resolves #CF upgrade for deploys across all repos openFEC#6110
Required reviewers
1 developer
Impacted areas of the application
Screenshots
Before:
cf cli v7.0.1 circleci build:
After:
cf cli v8.9.0. circleci build:
Related PRs
Related PRs against other branches:
How to test
brew install cloudfoundry/tap/cf-cli@8
cf version
installs for deploy
section, verify that cf cli v8.9.0 is downloaded and no errors theredeploy cms
section, verify that cms app deployed to cloud.space successfully without any errorsdeploy cms
section` confirm that cms app is using Cloud Foundry v3 API: