feat(dashboard, application-generic): introduce new regions and regioncontext to launchdarkly fixes NV-6852 #9455
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.
This pull request introduces significant improvements to how regional context is handled for feature flagging and deployment, particularly with LaunchDarkly and AWS regions. The changes ensure that region information is consistently passed through both the frontend and backend, and expand deployment environment support to additional AWS regions.
Key changes include:
Feature flag context improvements:
feature-flags-provider.tsxnow includes aregionobject, withawsRegiondynamically detected from the URL and region config, and the context kind switched to'multi'for better multi-dimensional targeting.identity-provider.tsx, user and organization identification for LaunchDarkly now includes the current region, usingselectedRegionfrom context andgetRegionConfig, ensuring LaunchDarkly receives accurate region data on user/org identification. [1] [2] [3] [4]launch-darkly.service.ts) now adds aregioncontext ifNOVU_REGIONis set in the environment, aligning backend and frontend context structure.Deployment workflow enhancements:
deploy.yml) adds support for new AWS regions—London, Singapore, Australia, Japan, and Korea—across both staging and production, and updates environment mappings accordingly. [1] [2] [3]Provider context composition fix:
root.tsxwas corrected so thatIdentityProvideris now nested insideRegionProvider, ensuring region context is available when identifying users and organizations.