DC:255 Migrate IOptions<T> to IOptionsMonitor<T> for live AppConfig reload#141
Open
spokenbird wants to merge 1 commit intomainfrom
Open
DC:255 Migrate IOptions<T> to IOptionsMonitor<T> for live AppConfig reload#141spokenbird wants to merge 1 commit intomainfrom
spokenbird wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or 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
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.
IOptions<T>(singleton-cached) toIOptionsMonitor<T>so AWS AppConfig changes are picked up withoutredeploying ECS tasks
SocureSettingsDI registration from singleton to transient factory viaIOptionsMonitor, preserving clean layering (UseCases layer still injects plainSocureSettings)Settings affected
IdProofingRequirementsSettings— IAL requirementsSocureSettings— stub/live toggle, URLsSmartySettings/AddressValidationPolicySettings— address validationStateHouseholdIdSettings— Email vs Phone household lookupWhat's NOT changed (intentionally)
JwtSettings— changing signing keys at runtime would invalidate active sessionsSeedingSettings— seeds once at startup; fixed via env var insteadIdentifierHasherSettings— security-sensitive, singleton is appropriateTest plan
takes effect without redeployment