Fix module reference in DAG example

[therealgglggl]

output.tf should be under foo folder since foo is providing the output

Description

Fixes #000.

TODOs

Read the Gruntwork contribution guidelines.

• I authored this code entirely myself
• I am submitting code based on open source software (e.g. MIT, MPL-2.0, Apache)]
• I am adding or upgrading a dependency or adapted code and confirm it has a compatible open source license
• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].

Migration Guide

Summary by CodeRabbit

• Documentation
  • Updated quick start guide examples to ensure accuracy and consistency with current system structure.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

@therealgglggl is attempting to deploy a commit to the Gruntwork Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation file updated to change a dependency example from the shared module to the foo module, including corresponding updates to output block file paths and accompanying commentary.

Changes

Cohort / File(s)	Summary
Getting Started Documentation docs-starlight/src/content/docs/01-getting-started/01-quick-start.mdx	Updated dependency example references from shared module to foo module; output block path changed from shared/output.tf to foo/output.tf with related path commentary adjustments

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• denis256
• yhakbar

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: fixing a module reference in a DAG example by moving output.tf to the correct foo module folder.
Description check	✅ Passed	The description includes the template structure with sections for Description, TODOs, and Release Notes, though some sections lack detail.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs-starlight/src/content/docs/01-getting-started/01-quick-start.mdx (1)

365-372: Minor clarity tweak: “foo unit” vs “foo module”

Since the Terraform source is ../shared, calling foo a “module” here may be confusing—foo is the Terragrunt unit. Consider adjusting the sentence to make that explicit.

Proposed doc tweak

-For example, let's say that the `content` of the `bar` unit depended on the `content` of the `foo` unit. You can express this dependency first by adding an `output` block to the `foo` module:
+For example, let's say that the `content` of the `bar` unit depended on the `content` of the `foo` unit. You can express this dependency first by adding an `output` block to the Terraform configuration for the `foo` unit (e.g., `foo/output.tf`):

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e0a2f68 and aaa949b.

📒 Files selected for processing (1)

• docs-starlight/src/content/docs/01-getting-started/01-quick-start.mdx

🧰 Additional context used

📓 Path-based instructions (1)

docs-starlight/**/*.md*

⚙️ CodeRabbit configuration file

Review the documentation for clarity, grammar, and spelling. Make sure that the documentation is easy to understand and follow. There is currently a migration underway from the Jekyll based documentation in docs to the Starlight + Astro based documentation in docs-starlight. Make sure that the docs-starlight documentation is accurate and up-to-date with the docs documentation, and that any difference between them results in an improvement in the docs-starlight documentation.

Files:

• docs-starlight/src/content/docs/01-getting-started/01-quick-start.mdx