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

Add feature flag for the API summary content change #4643

Conversation

tomas-stefano
Copy link
Contributor

@tomas-stefano tomas-stefano commented Oct 31, 2024

Context

There is inconsistency of terminology between GiT and Find. GiT use “QTS with PGDE” (which is more clear/intuitive) whereas Find uses “PGDE with QTS”.

It was decided by Apply and Find teach leads to change the API content of the course description to the expected ones (PGCE with QTS becomes QTS with PGCE and PGDE with QTS becomes QTS with PGDE).

This is a simple PR that just adds the feature flag.

Will be false as default in all environments.

Plan

  1. Merge the feature flag PR (this PR!)
  2. Merge the code that uses the feature flag (Replace instances of PGDE with QTS / change API course summary #4645 )
  3. Turn on the feature flag on QA when having a session with Register & Apply (needs a PR and deployment)
  4. Have the Register & Apply sign off that everything worked
  5. Turn on the feature flag on Production (needs a deployment) and also deploy the API docs change here about the content change on API on the history/updates section.

Will be default to false as default.

Plan:

Merge the add feature flag PR
Merge the code that uses the feature flag
Turn on the feature flag on QA when having a session with Register & Apply (needs a deployment)
Have the Register & Apply sign off that everything worked
Turn on the feature flag on Production (needs a deployment)
@tomas-stefano tomas-stefano requested a review from a team as a code owner October 31, 2024 20:38
@@ -89,6 +89,7 @@ feedback:
link: https://forms.office.com/pages/responsepage.aspx?id=yXfS-grGoU2187O4s0qC-SKECobyE75EtuJMp8rYxZtURTNaTTJaTVhBQlQzM1RESTJDVlBERk1JQS4u

features:
api_summary_content_change: false
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you ask why a feature flag for a content change on the API?

Thousands of courses will be updated in Apply (confirmed already in the DB) and maybe on Register too.

So I optin for the feature flag approach (see PR description for more info on the plan).

for you awareness @Nitemaeric

@tomas-stefano
Copy link
Contributor Author

@tomas-stefano tomas-stefano merged commit ab45c2b into main Nov 4, 2024
38 checks passed
@tomas-stefano tomas-stefano deleted the td/33-replace-instances-of-pgde-with-qts-to-qts-with-pgde branch November 4, 2024 11:58
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

Successfully merging this pull request may close these issues.

2 participants