CF upgrade for deploys across all repos

[patphongs]

What we’re after

The cloud.gov CloudFoundry API is shifting from V2 to V3. V2 will be fully deprecated and disabled by June 7, 2025. Before that, in February 2025, there will be "brownout" periods where the V2 endpoint is disabled for testing purposes.

To ensure continuity, we need to upgrade our cf cli version to at least v7.7.1, which supports V3. This upgrade could impact plugins we’re using, so we need to review and address any plugin issues. Plugin status should be verified during this process.

While most of our builds appear to be using API version 3, some repositories haven't been deployed recently, and CircleCI logs are not available for confirmation:

• fec-cms: v3.182.0 v3.185.0
• openfec: v3.182.0 v3.185.0
• fec-proxy: v3.181.0
• fec-proxy-redirect: ?
• fec-pattern-library: ?

CF CLI Versions
All repositories are currently using CF CLI version 7.1:

• fec-cms
• openfec
• fec-proxy
• fec-proxy-redirect
• fec-pattern-library

Action item(s)

• Upgrade cf cli to at least v7.7.1 in all repositories.
• Verify API version usage in fec-proxy-redirect and fec-pattern-library.
• Test and confirm plugin compatibility with the upgraded cf cli version.
• Run deployment tests on all repositories to confirm successful upgrades.
• Review and update CircleCI configuration files to ensure compatibility with V3 API.
• Document any issues encountered and their resolution (No issues to report)

---

Completion criteria

• All repositories are using cf cli version v7.7.1 or higher.
• API version 3 is confirmed for all repositories.
• Plugin compatibility is verified and resolved if necessary.
• Successful deployments have been tested and documented.
• CircleCI configurations are updated and functional.

[pkfec]

CF CLI releases :https://github.com/cloudfoundry/cli/releases

cf target -s <space name > will display the https://api.fr.cloud.gov/ version on cloud.gov spaces. Dev, Stage, Prod spaces are already using Cloud foundry API v3.185.0

F612211M:fec-proxy-redirect pkasireddy$ cf target -s dev
API endpoint:   https://api.fr.cloud.gov
API version:    3.185.0
user:           pkasireddy@fec.gov
org:            fec-beta-fec
space:          dev

[pkfec]

APP name	CloudFoundry API	CloudFoundry API v3	CF CLI v8 support CF API v3 (Upgraded version)	CF CLI v7 still use CF API v2 (current)
fec-proxy	https://api.fr.cloud.gov	3.185.0	8.9.0	7.1.0
fec-proxy-redirect	https://api.fr.cloud.gov	3.185.0	8.9.0	7.1.0
fec-pattern-library	https://api.fr.cloud.gov	3.185.0	8.9.0	7.1.0
fec-cms	https://api.fr.cloud.gov	3.185.0	8.9.0	7.1.0
openFEC	https://api.fr.cloud.gov	3.185.0	8.9.0	7.1.0

[pkfec]

I deployed the following apps to the dev space and verified that all of them are using the Cloud Foundry v3 API.

• openFEC
• fec-cms
• fec-pattern-library
• fec-proxy
• fec-proxy-redirect

[pkfec]

3rd party plugins: https://cloud.gov/2025/01/07/v2api-deprecation/#plugin-status

Plugin	v3 Compatible?	FEC usage
app-autoscaler-plugin	Yes	No
cf-service-connect	Pending	We moved away from this plugin. Use SSH to connect to CMS app
log-cache-cli plugin	Pending	No
stack-auditor plugin	Pending	No
report-usage plugin	Pending	No
cf-route-lookup	No, use cf routes instead	We use cf routes, works as expected
deploy		works as expected
top plugin	No, this is an admin-only tool, no replacement expected	No
statistics plugin	No, project appears abandoned	No