You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2021. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: