Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughIntroduced a new Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/src/data/changelog/v1.0.1.mdx (1)
38-38: Consider broadening the subsection title for precision.Line 38 currently frames this as unit wiring only; the body also covers stack-level dependency behavior. A title like “Dependency wiring across units and stacks” would be clearer.
As per coding guidelines, docs should be clear and easy to follow.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/src/data/changelog/v1.0.1.mdx` at line 38, Update the subsection title currently written as `stack-dependencies` to a clearer, broader heading that reflects both unit and stack-level behavior—e.g., change it to "Dependency wiring across units and stacks" so the title matches the body content discussing stack-level dependency behavior; update the header text where `stack-dependencies` appears to the new phrasing.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/src/data/experiments/stack-dependencies.mdx`:
- Around line 9-18: Update the documentation for the `stack-dependencies`
experiment to clarify that `terragrunt.autoinclude.hcl` is deep-merged into both
unit and stack configurations (not just unit configurations); edit the sentence
that currently reads “Automatic deep merge of `terragrunt.autoinclude.hcl` into
unit configurations (autoinclude wins)” to explicitly say “Automatic deep merge
of `terragrunt.autoinclude.hcl` into unit and stack configurations (autoinclude
wins)” so it references both targets and preserves the “autoinclude wins”
precedence.
---
Nitpick comments:
In `@docs/src/data/changelog/v1.0.1.mdx`:
- Line 38: Update the subsection title currently written as `stack-dependencies`
to a clearer, broader heading that reflects both unit and stack-level
behavior—e.g., change it to "Dependency wiring across units and stacks" so the
title matches the body content discussing stack-level dependency behavior;
update the header text where `stack-dependencies` appears to the new phrasing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 9412263e-b62a-43cb-a205-d55a6fc51abe
📒 Files selected for processing (3)
docs/src/data/changelog/v1.0.1.mdxdocs/src/data/experiments/stack-dependencies.mdxinternal/experiment/experiment.go
Comment on lines
+9
to
+18
| ### `stack-dependencies` - What it does | ||
| When enabled, this experiment adds support for the `autoinclude` block nested inside `unit` and `stack` blocks in `terragrunt.stack.hcl` files. The `autoinclude` block allows users to define `dependency` blocks and arbitrary configuration that gets generated into a `terragrunt.autoinclude.hcl` file during stack generation. This file is automatically merged into the unit/stack configuration when parsed. | ||
|
|
||
| This experiment enables: | ||
|
|
||
| - **`unit.<name>.path`** and **`stack.<name>.path`** variables in `terragrunt.stack.hcl` for referencing sibling component paths | ||
| - **`stack.<name>.<unit_name>.path`** for referencing individual units within a nested stack (fine-grained dependency) | ||
| - **`dependency` blocks targeting stack directories** — aggregated outputs from all units in the stack (`dependency.stack_name.outputs.unit_name.output_key`) | ||
| - **Automatic deep merge** of `terragrunt.autoinclude.hcl` into unit configurations (autoinclude wins) | ||
| - **Stack dependency expansion** in the run queue — depending on a stack blocks until all its units complete |
Contributor
There was a problem hiding this comment.
Clarify merge target to include stack configs at Line 17.
Line 17 currently says deep merge into unit configurations only, but this experiment behavior applies to both unit and stack configurations.
✏️ Proposed doc fix
-- **Automatic deep merge** of `terragrunt.autoinclude.hcl` into unit configurations (autoinclude wins)
+- **Automatic deep merge** of `terragrunt.autoinclude.hcl` into unit and stack configurations (autoinclude wins)As per coding guidelines, this doc must state that terragrunt.autoinclude.hcl is deep-merged into unit/stack config with “autoinclude wins” precedence.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ### `stack-dependencies` - What it does | |
| When enabled, this experiment adds support for the `autoinclude` block nested inside `unit` and `stack` blocks in `terragrunt.stack.hcl` files. The `autoinclude` block allows users to define `dependency` blocks and arbitrary configuration that gets generated into a `terragrunt.autoinclude.hcl` file during stack generation. This file is automatically merged into the unit/stack configuration when parsed. | |
| This experiment enables: | |
| - **`unit.<name>.path`** and **`stack.<name>.path`** variables in `terragrunt.stack.hcl` for referencing sibling component paths | |
| - **`stack.<name>.<unit_name>.path`** for referencing individual units within a nested stack (fine-grained dependency) | |
| - **`dependency` blocks targeting stack directories** — aggregated outputs from all units in the stack (`dependency.stack_name.outputs.unit_name.output_key`) | |
| - **Automatic deep merge** of `terragrunt.autoinclude.hcl` into unit configurations (autoinclude wins) | |
| - **Stack dependency expansion** in the run queue — depending on a stack blocks until all its units complete | |
| ### `stack-dependencies` - What it does | |
| When enabled, this experiment adds support for the `autoinclude` block nested inside `unit` and `stack` blocks in `terragrunt.stack.hcl` files. The `autoinclude` block allows users to define `dependency` blocks and arbitrary configuration that gets generated into a `terragrunt.autoinclude.hcl` file during stack generation. This file is automatically merged into the unit/stack configuration when parsed. | |
| This experiment enables: | |
| - **`unit.<name>.path`** and **`stack.<name>.path`** variables in `terragrunt.stack.hcl` for referencing sibling component paths | |
| - **`stack.<name>.<unit_name>.path`** for referencing individual units within a nested stack (fine-grained dependency) | |
| - **`dependency` blocks targeting stack directories** — aggregated outputs from all units in the stack (`dependency.stack_name.outputs.unit_name.output_key`) | |
| - **Automatic deep merge** of `terragrunt.autoinclude.hcl` into unit and stack configurations (autoinclude wins) | |
| - **Stack dependency expansion** in the run queue — depending on a stack blocks until all its units complete |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/src/data/experiments/stack-dependencies.mdx` around lines 9 - 18, Update
the documentation for the `stack-dependencies` experiment to clarify that
`terragrunt.autoinclude.hcl` is deep-merged into both unit and stack
configurations (not just unit configurations); edit the sentence that currently
reads “Automatic deep merge of `terragrunt.autoinclude.hcl` into unit
configurations (autoinclude wins)” to explicitly say “Automatic deep merge of
`terragrunt.autoinclude.hcl` into unit and stack configurations (autoinclude
wins)” so it references both targets and preserves the “autoinclude wins”
precedence.
yhakbar
approved these changes
Apr 8, 2026
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
2 participants
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.
Description
RFC: #5663
TODOs
Read the Gruntwork contribution guidelines.
Release Notes (draft)
Added / Removed / Updated [X].
Migration Guide
Summary by CodeRabbit
New Features
Documentation