Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spike: Research implications of CF API v2 deprecation (remediation due March 3, 2025) #1291

Open
exalate-issue-sync bot opened this issue Jan 21, 2025 · 5 comments
Assignees

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Jan 21, 2025

https://cloud.gov/2025/01/07/v2api-deprecation/

  • Research other needed changes
    • identify if connect-to-service plugin will be supported
    • identify CF CLI commands that we run and whether they are still supported with v3
  • At minimum, update cf cli in Circle to 7.7 or higher, or latest V7 for web app, API, and proxy
  • Create tickets, put them in sprint 56

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1959

@exalate-issue-sync exalate-issue-sync bot changed the title Spike: Research implications of CF API v2 deprecation Spike: Research implications of CF API v2 deprecation (due March '25) Jan 22, 2025
@exalate-issue-sync exalate-issue-sync bot changed the title Spike: Research implications of CF API v2 deprecation (due March '25) Spike: Research implications of CF API v2 deprecation (remediation due March '25) Jan 22, 2025
@exalate-issue-sync exalate-issue-sync bot changed the title Spike: Research implications of CF API v2 deprecation (remediation due March '25) Spike: Research implications of CF API v2 deprecation (remediation due March 3, 2025) Jan 27, 2025
Copy link
Author

exalate-issue-sync bot commented Feb 3, 2025

David Heitzer commented: We are using the web api directly in our rollback devops commands [here|https://github.com/fecgov/fecfile-web-app/blob/e4fcd61defdd09b5c0105be6eb60a102f6fa9f79/tasks.py#L178] and [here|https://github.com/fecgov/fecfile-web-api/blob/31d6fede61b1ada7e915fdab8d55fcff43681e0f/tasks.py#L139] however we are using v3 already in those URLs so those do not need updated.

We are also using the web api in our api utils module however [this also uses the v3 url|https://github.com/fecgov/fecfile-web-api/blob/31d6fede61b1ada7e915fdab8d55fcff43681e0f/django-backend/fecfiler/devops/utils/cf_api_utils.py#L6]

We have also confirmed that all of our following used commands are available in the latest CF CLI v7 (7.8.0) using:

!image-20250203-211741.png|width=920,height=498,alt="image-20250203-211741.png"!

…many more pages of commands to cross-reference against our cf commands used in tasks.py and other places.

The only update we need to make therefore is to upgrade our CF CLI version used by CircleCI to the latest V7. This ticket is [here|https://fecgov.atlassian.net/browse/FECFILE-2001].

Copy link
Author

Todd Lees commented: Excellent news!

Copy link
Author

Todd Lees commented: Research complete. related tickets are established

Copy link
Author

Shelly Wise commented: No QA review needed on this ticket per DEV.

Moved to Stage Ready.

Copy link
Author

exalate-issue-sync bot commented Feb 10, 2025

David Heitzer commented: verified that cf connect-to-service works with 7.8.0:

{noformat}heitzerd@heitzerd-HP-ENVY-TE01-2xxx:/tmp/cftest$ ./cf --version
cf version 7.8.0+cb395bf.2024-12-02
heitzerd@heitzerd-HP-ENVY-TE01-2xxx:/tmp/cftest$ ./cf connect-to-service -no-client fecfile-web-api fecfile-api-rds
Finding the service instance details...
Setting up SSH tunnel...
SSH tunnel created.{noformat}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants