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

Deprecate the old (v1) API #1449

Open
12 tasks
jgadling opened this issue Jan 8, 2025 · 0 comments
Open
12 tasks

Deprecate the old (v1) API #1449

jgadling opened this issue Jan 8, 2025 · 0 comments
Labels

Comments

@jgadling
Copy link
Contributor

jgadling commented Jan 8, 2025

Once the frontend has been fully migrated to the new (v2) api, we need to tear down the infrastructure that supports the old API:

  • Review service logs for APIv1 to ensure it's not being used by any critical services
    • Work with CZII/Product to communicate the upcoming deprecation to any APIv1 users we can identify
  • Disable any GitHub actions that deploy the APIv1
  • Delete the happy stacks for APIv1 in staging and prod
  • Wait a few days to ensure all systems are still working well
  • Remove any happy configuration code from the cryoet-data-portal-backend repository
  • Remove any apiv1 code from the cryoet-data-portal-backend repository
    • remove apiv1 itself
    • remove references to the apiv1 database/app (e.g. the v1 db ingestion scripts, and references to them from workflows)

If the frontend has already been migrated to Argus at this point, we should tear down the happy infrastructure in our accounts entirely:

  • Reach out to #help-infra to see if there are any concerns/steps we need to take to do this properly.
  • Remove the dev/staging happy infrastructure from our cryoet-infra repository. Review the TF plans to make sure they won't break our argus services, and apply the changes.
  • Remove the prod happy infrastructure from our cryoet-infra repository
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant