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.

Sign up for GitHub

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

Jump to bottom

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 · 0 comments
Open

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

exalate-issue-sync bot opened this issue Jan 21, 2025 · 0 comments
Assignees
@toddlees @dheitzer

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Jan 21, 2025 •
edited
Loading

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@toddlees toddlees

@dheitzer dheitzer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@toddlees @dheitzer