Add a new feature flag for AYTQ #458
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Follow up work for this is in #455 |
We want separate feature flags controlling access to each service in this app rather than a single one. This will give us more granular control over releasing the apps to the public. As AYTQ is already a live service, we need to introduce the new flag for it and set it to active before deploying the changes to use the new flag. This will allow us to seamlessly make the switch to the new names without interruption to the live service.
felixclack
force-pushed
the
add-new-feature-flags
branch
from
517ce19 to
b199d3b
Compare
gpeng
approved these changes
Dec 5, 2023
felixclack
added a commit
that referenced
this pull request
Dec 5, 2023
Add a new feature flag for AYTQ
felixclack
added a commit
that referenced
this pull request
Dec 5, 2023
Revert "Merge pull request #458 from DFE-Digital/add-new-feature-flags"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want separate feature flags controlling access to each service in this app
rather than a single one.
This will give us more granular control over releasing the apps to the
public.
As AYTQ is already a live service, we need to introduce the new flag for
it and set it to active before deploying the changes to use the new
flag.
This will allow us to seamlessly make the switch to the new names
without interruption to the live service.