Doc: explicit the influence of mock_outputs_merge_strategy_with_state when a state exists #4529
Conversation
… a state exists Builds on feedback obtained in gruntwork-io#4521
📝 WalkthroughWalkthroughThe documentation for the Changes
Sequence Diagram(s)No sequence diagram generated as the changes are limited to documentation updates. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ajoga
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/_docs/04_reference/04-config-blocks-and-attributes.md (2)
1245-1246: Refine wording for precision and flowSmall re-phrase makes the sentence crisper and removes the parenthetical pause.
-The value of `mock_outputs_merge_strategy_with_state` defines how mocks are combined (or not) with outputs from an -existing state. +The `mock_outputs_merge_strategy_with_state` attribute determines how mock outputs are combined—or deliberately +not combined—with the outputs obtained from an existing state.
1255-1256: Tighten bullet text & apply “as-is” conventionMinor style/grammar tweaks while keeping semantics unchanged.
- - `no_merge` (default) - any existing state will be used as is. If the dependency does not have an existing state (it - hasn't been applied yet), then the mocks will be used. If a state exists, then the mocks will not be used. + - `no_merge` (default) – use the existing state **as-is**. Mocks are used only when no state file is present + (e.g., the dependency has not been applied yet).
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/_docs/04_reference/04-config-blocks-and-attributes.md(2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/**/*.md
Instructions used from:
Sources:
⚙️ CodeRabbit Configuration File
🔇 Additional comments (1)
docs/_docs/04_reference/04-config-blocks-and-attributes.md (1)
1245-1256: Mirror the change indocs-starlightPer the migration guideline, please replicate the above edits in the equivalent
docs-starlightmarkdown so both doc sets stay in sync.
Description
Explicit the influence of mock_outputs_merge_strategy_with_state when a state exists
Builds on feedback obtained in #4521
TODOs
Read the Gruntwork contribution guidelines.
Summary by CodeRabbit
mock_outputs_merge_strategy_with_stateattribute in thedependencyblock.no_mergestrategy to explicitly state that mocks are not used when a state exists.