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.

Sign up for GitHub

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

Jump to bottom

Update terragrunt version #1884

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from
Open

Update terragrunt version #1884

wants to merge 4 commits into from

Conversation

ps-occrp
Copy link

@ps-occrp ps-occrp commented Feb 20, 2025 •
edited by coderabbitai bot
Loading

Update action to use newer version of terragrunt as default

Summary by CodeRabbit

  • Chores

    • Upgraded the default Terragrunt integration to version v0.73.7, providing enhanced performance and improved compatibility with current standards.
    • Added new environment variables for caching, improving clarity and organization.

  • Refactor

    • Standardized configuration naming and refined logging outputs, resulting in clearer diagnostics and better maintainability.

These improvements help ensure a more robust and predictable user experience while supporting ongoing system enhancements. These updates further solidify infrastructure stability and align with best practices.

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 20, 2025 •
edited
Loading

Walkthrough

This pull request updates several file configurations to improve nomenclature consistency and upgrade dependencies. In the workflow configuration (action.yml), the default Terragrunt version is upgraded, and several environment variable names are shortened. The digger module sees reorganized import statements and updated logging to reflect the new variable names. The Terragrunt execution logic now uses updated environment variable names consistently in setting up command execution.

Changes

Files Change Summary
action.yml Updated terragrunt-version default from v0.55.5 to v0.73.7; added env vars TG_PROVIDER_CACHE_DIR and TG_PROVIDER_CACHE.
cli/.../digger.go Reorganized import statements; modified logging statement to reference TG_PROVIDER_CACHE_DIR instead of TERRAGRUNT_PROVIDER_CACHE_DIR.
libs/.../terragrunt.go Renamed env vars in runTerragruntCommand: TERRAGRUNT_NO_COLOR → TG_NO_COLOR, TERRAGRUNT_NON_INTERACTIVE → TG_NON_INTERACTIVE, added TG_TF_FORWARD_STDOUT.

Possibly related PRs

  • Update action.yml #1856: The changes in the main PR are related to the modifications in the action.yml file, specifically regarding the environment variables used for caching, which aligns with the caching mechanism updates in the retrieved PR.
  • allow cache values to be overridable for terraform and terragrunt #1873: The changes in the main PR are related to the modifications of environment variables in action.yml, which are also referenced in the logging updates in the digger.go file of the retrieved PR.

Poem

I'm a rabbit with a coding hop,
Watching old names merrily drop.
Upgraded versions lead my dance,
Clean logs and vars now enhance.
With carrot dreams, I leap in code!
🥕🐇

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 808de7d and 8e3fda5.

📒 Files selected for processing (3)
  • action.yml (5 hunks)
  • cli/pkg/digger/digger.go (2 hunks)
  • libs/execution/terragrunt.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • libs/execution/terragrunt.go
  • action.yml
  • cli/pkg/digger/digger.go

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ps-occrp ps-occrp changed the base branch from main to develop February 20, 2025 12:57
greptile-apps[bot]
greptile-apps bot reviewed Feb 20, 2025
View reviewed changes
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This PR represents a major restructuring of the Digger codebase, moving from a flat pkg-based structure to a modular organization with separate backend, CLI, and enterprise edition components.

Key changes:

  • Moved core functionality from pkg/ to libs/, backend/, cli/, and ee/ directories for better code organization
  • Added new database migrations and models for enhanced project management and drift detection
  • Introduced new CI backend implementations for GitHub Actions, GitLab, and Buildkite
  • Added comprehensive documentation in docs/ covering features, cloud providers, and enterprise capabilities
  • Updated Terragrunt version to v0.73.7 in action.yml

💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!

640 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile

motatoes
motatoes reviewed Feb 21, 2025
View reviewed changes
motatoes
motatoes reviewed Feb 21, 2025
View reviewed changes
motatoes
motatoes reviewed Feb 21, 2025
View reviewed changes
motatoes
motatoes reviewed Feb 21, 2025
View reviewed changes
motatoes
motatoes requested changes Feb 21, 2025
View reviewed changes
Copy link
Contributor

@motatoes motatoes left a comment

Choose a reason for hiding this comment

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

Hi thanks for your contribution! Please address the comments to maintain backwards compatability with older versions of terragrunt

ps-occrp and others added 3 commits February 21, 2025 13:50
@ps-occrp
Copy link
Author

Hi @motatoes I have adopted PR to support backward compatibility

@ps-occrp ps-occrp requested a review from motatoes February 21, 2025 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@greptile-apps greptile-apps[bot]

@motatoes motatoes

Requested changes must be addressed to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ps-occrp @motatoes