Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Reorganizing the features section of the docs #3640

Open
wants to merge 21 commits into
base: main
Choose a base branch
from

Conversation

yhakbar
Copy link
Collaborator

@yhakbar yhakbar commented Dec 9, 2024

Description

Reoganizes the Features section of the docs.

It reduces the emphasis on "DRY", and focuses more on the modern features of Terragrunt that make it a good orchestrator.

TODOs

Read the Gruntwork contribution guidelines.

  • Update the docs.
  • Run the relevant tests successfully, including pre-commit checks.
  • Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
  • Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Updated Features section of docs.

@yhakbar
Copy link
Collaborator Author

yhakbar commented Dec 9, 2024

Current Site:

before

WIP After:

wip-after

@yhakbar yhakbar marked this pull request as ready for review December 10, 2024 22:31
@yhakbar yhakbar force-pushed the chore/reorganize-features branch from 5f812d6 to 396a898 Compare December 10, 2024 23:34
@yhakbar yhakbar force-pushed the chore/reorganize-features branch from 396a898 to a11bbad Compare December 10, 2024 23:34

**Note:** During `destroy` runs, Terragrunt will try to find all dependent units and show a confirmation prompt with a list of detected dependencies. This is because Terragrunt knows that once resources in a dependency is destroyed, any commands run on dependent units may fail. For example, if `destroy` was called on the `redis` unit, you'll be asked for confirmation, as the `backend-app` depends on `redis`. You can avoid the prompt by using `--terragrunt-non-interactive`.

## Visualizing the DAG
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is DAG a universal enough acronym to use without nearby definition?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants