Integration: Strict Environment Supremacy Validation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- testing
Research direction
This issue targets the top-level RolloutStateMachine; first resolve or review blocked issue #125, then locate the existing integration-test entry point. Add the Local → Remote → Env scenario, trigger the remote hot-reload, and verify that the delivered configuration keeps bla = c.
Written by the indexing model from the issue text.
Description
Description
Establish the "Strict Environment Supremacy" integration test suite. This slice explicitly tests the full top-level RolloutStateMachine to guarantee that runtime hot-reloads correctly respect the existing configuration merge hierarchy (Local -> Remote -> Env). Construct a specific integration scenario: Configure a local setting (bla = a), an initial remote setting (bla = b), and an environment variable (bla = c). Trigger a hot-reload with a new remote configuration (bla = d). Verify that the final merged configuration delivered to the application still strictly resolves bla = c.
Acceptance criteria
-
A top-level integration test is implemented simulating the Local -> Remote -> Env hierarchy.
-
Hot-reloading a remote value that conflicts with a local environment variable correctly discards the remote value in favor of the environment variable.
Blocked by
Issue #125
User stories covered: 7
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MapColonies/config
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MapColonies/config#128 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
MapColonies/config#127 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 38/100
MapColonies/config#126 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
MapColonies/config#125 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MapColonies/config#75 ·
All issues in MapColonies/config
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
ehmpathy/rhachet-roles-bhrain#586 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OHDSI/Data2Evidence#3496 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/rocketmq-dashboard#5594 ·
Maintainers usually reply within 3 days
-
react-doctor severity:warning tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 88/100
digidem/comapeo-cloud-app#418 ·
Maintainers usually reply within 1 day