Skip to content
This repository has been archived by the owner on May 7, 2021. It is now read-only.

Disable redirects before a release #2179

Open
ngosset opened this issue Aug 10, 2020 · 0 comments
Open

Disable redirects before a release #2179

ngosset opened this issue Aug 10, 2020 · 0 comments
Assignees
Labels

Comments

@ngosset
Copy link
Contributor

ngosset commented Aug 10, 2020

Right now we don't have an effective way to ensure we aren't causing issues with users when we deploy. We rely on google analytics or waiting until we've hit our maximum # of reports for the day.

The "Gold Standard" would be a zero-downtime deployment in our release pipeline where it's entirely transparent to the users and the API is versioned.

However a much more attainable version for us would be:

Disable CAFC redirect by setting a database flag to false (or other means)
Wait 1-2 hours
Deploy new version
Re-enable redirect by setting a database flag back to true (or other means)

We need a developer to add a flag to the database, and edit the isAvailable code to check that this flag is true before accepting a redirect.

@ngosset ngosset added bug Something isn't working high priority technical debt labels Aug 10, 2020
@ying-chen-cds ying-chen-cds self-assigned this Aug 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants