-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update github (minor) #82
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/github
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
renovate
bot
changed the title
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 - autoclosed
Feb 25, 2024
renovate
bot
changed the title
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 - autoclosed
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2
Feb 27, 2024
renovate
bot
force-pushed
the
renovate/github
branch
from
February 27, 2024 06:21
70d1ddc
to
471e261
Compare
renovate
bot
changed the title
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 - autoclosed
Feb 27, 2024
renovate
bot
changed the title
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 - autoclosed
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2
Feb 29, 2024
renovate
bot
changed the title
fix(deps): update github.com/davecgh/go-spew digest to 8991bc2
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0
Feb 29, 2024
renovate
bot
force-pushed
the
renovate/github
branch
from
February 29, 2024 22:30
471e261
to
d110f36
Compare
renovate
bot
changed the title
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0
fix(deps): update github
Mar 19, 2024
renovate
bot
changed the title
fix(deps): update github
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0
Mar 19, 2024
renovate
bot
changed the title
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0
fix(deps): update github
Mar 21, 2024
renovate
bot
changed the title
fix(deps): update github
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0
Mar 21, 2024
renovate
bot
changed the title
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.1
Mar 26, 2024
renovate
bot
force-pushed
the
renovate/github
branch
from
March 26, 2024 19:49
d110f36
to
c1ba913
Compare
renovate
bot
changed the title
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.1
fix(deps): update github
Mar 27, 2024
renovate
bot
changed the title
fix(deps): update github
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.1
Mar 27, 2024
renovate
bot
force-pushed
the
renovate/github
branch
from
April 4, 2024 19:24
c1ba913
to
1de6418
Compare
renovate
bot
changed the title
fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.1
fix(deps): update github (minor)
Apr 4, 2024
renovate
bot
changed the title
fix(deps): update github (minor)
fix(deps): update github
Apr 6, 2024
renovate
bot
changed the title
fix(deps): update github
fix(deps): update github (minor)
Apr 6, 2024
renovate
bot
force-pushed
the
renovate/github
branch
2 times, most recently
from
April 10, 2024 17:56
db79e7c
to
c21d008
Compare
renovate
bot
force-pushed
the
renovate/github
branch
6 times, most recently
from
December 4, 2024 16:10
140e7d8
to
495856a
Compare
renovate
bot
force-pushed
the
renovate/github
branch
4 times, most recently
from
December 11, 2024 15:25
c71b106
to
afd85f6
Compare
renovate
bot
force-pushed
the
renovate/github
branch
8 times, most recently
from
December 19, 2024 01:32
552ac92
to
b83ace2
Compare
renovate
bot
force-pushed
the
renovate/github
branch
from
December 20, 2024 17:36
b83ace2
to
306354f
Compare
renovate
bot
force-pushed
the
renovate/github
branch
6 times, most recently
from
January 10, 2025 16:54
d212766
to
203bfe2
Compare
renovate
bot
force-pushed
the
renovate/github
branch
3 times, most recently
from
January 15, 2025 18:53
dc4edbb
to
003c66d
Compare
renovate
bot
force-pushed
the
renovate/github
branch
from
January 16, 2025 19:26
003c66d
to
74c9ec4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
v1.16.0
->v1.18.0
v0.55.1
->v0.72.2
v2.19.1
->v2.23.0
a34142e
->c404f82
v0.20.0
->v0.21.0
v0.21.0
->v0.24.0
v6.5.4
->v6.6.5
v1.3.0
->v1.4.2
v1.18.2
->v1.19.0
v1.14.2
->v1.16.1
Release Notes
fatih/color (github.com/fatih/color)
v1.18.0
Compare Source
What's Changed
New Contributors
Full Changelog: fatih/color@v1.17.0...v1.18.0
v1.17.0
Compare Source
What's Changed
New Contributors
Full Changelog: fatih/color@v1.16.0...v1.17.0
gruntwork-io/terragrunt (github.com/gruntwork-io/terragrunt)
v0.72.2
Compare Source
✨ New Features
Stack
run
commandThe
terragrunt stack
command now supports a newrun
sub-command.The
run
command automatically generates a Terragrunt stack using theterragrunt.stack.hcl
file found in the currentTo try it out, make sure you enable the stacks experiment.
Read the docs to learn more.
Example usage:
Native OpenTofu State Encryption
Terragrunt now has native support for OpenTofu state encryption configurations.
In addition to the existing
backend
andconfig
attributes on theremote_state
configuration block, Terragrunt now supports anencryption
attribute that configures OpenTofu backend state encryption automatically, with type validation for a native experience using state encryption.The currently supported key providers are:
pbkdf2
aws_kms
gcp_kms
To integrate this new feature into your projects read the docs.
Special thanks for @norman-zon for taking on the work of integrating this into Terragrunt and collaborating with us on resolution!
What's Changed
stack run
command by @denis256 in https://github.com/gruntwork-io/terragrunt/pull/3762New Contributors
Full Changelog: gruntwork-io/terragrunt@v0.72.1...v0.72.2
v0.72.1
Compare Source
What's Changed
New Contributors
Full Changelog: gruntwork-io/terragrunt@v0.72.0...v0.72.1
v0.72.0
Compare Source
Description
OpenTofu 1.9 support: We are now testing Terragrunt against OpenTofu 1.9, and is confirmed to be working.
NOTE: Although this release is marked as backward incompatible, it is functionally compatible as nothing has been changed in Terragrunt internals. The minor version release is useful to mark the change in the OpenTofu version that is being tested.
What's Changed
TestDownloadTerraformSourceFromLocalFolderWithManifest
test by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/3744Full Changelog: gruntwork-io/terragrunt@v0.71.5...v0.72.0
v0.71.5
Compare Source
🔧 Fixes
Fixed bug that prevented OpenTofu/Terraform stdout from being streamed in real time.
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.71.4...v0.71.5
v0.71.4
Compare Source
✨ New Features
The
terraform
configuration block now accepts anexclude_from_copy
attribute that does the opposite of theinclude_in_copy
attribute.For more information, read the docs.
What's Changed
New Contributors
Full Changelog: gruntwork-io/terragrunt@v0.71.3...v0.71.4
v0.71.3
Compare Source
✨ New Features
The
terragrunt stack generate
command, now available behind the--experiment stacks
flag generates a.terragrunt-stack
directory by dynamically generating Terragrunt units from the configurations defined in aterragrunt.stack.hcl
file.To learn more, read the docs.
Example usage:
What's Changed
terragrunt stack generate
experiment by @denis256 in https://github.com/gruntwork-io/terragrunt/pull/3627Full Changelog: gruntwork-io/terragrunt@v0.71.2...v0.71.3
v0.71.2
Compare Source
What's Changed
%tf-command
log placeholder for custom format by @levkohimins in https://github.com/gruntwork-io/terragrunt/pull/3709New Contributors
Full Changelog: gruntwork-io/terragrunt@v0.71.1...v0.71.2
v0.71.1
Compare Source
What's Changed
log-disable-error-summary
flag by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/3687Full Changelog: gruntwork-io/terragrunt@v0.71.0...v0.71.1
v0.71.0
Compare Source
🔧 Fixes
Terragrunt stdout and stderr streams have been adjusted to more closely align with what users expect when using a tool orchestrating OpenTofu/Terraform.
For more information, read the following docs.
🛠️ Breaking Changes
While a bugfix, if you were relying on the incorrect behavior Terragrunt used, redirecting OpenTofu/Terraform stdout to stderr, you will experience a breaking change in this release.
To avoid having this be a breaking release, you can either use Terragrunt
stdout
instead ofstderr
for inspecting OpenTofu/Terraform stdout, or you can use stream redirection to reproduce the buggy behavior.terragrunt plan 1>&2
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.70.4...v0.71.0
v0.70.4
Compare Source
What's Changed
root-file-name
default forcatalog
andscaffold
by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/3682root
include forcatalog
andscaffold
by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/3683Full Changelog: gruntwork-io/terragrunt@v0.70.3...v0.70.4
v0.70.3
Compare Source
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.70.2...v0.70.3
v0.70.2
Compare Source
What's Changed
tf-command-args
support for custom log configuration by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/3679Full Changelog: gruntwork-io/terragrunt@v0.70.1...v0.70.2
v0.70.1
Compare Source
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.70.0...v0.70.1
v0.70.0
Compare Source
✨ New Features
Terragrunt now supports a native Experiment Mode to try out the latest features in Terragrunt before they're fully stable. Over time, we'll be moving some opt-in functionality to this system, and we'll be introducing new features behind it to give users granularity in their use of experimental functionality in Terragrunt.
As part of this new system, we'll also be documenting our experiments in much more detail so that you know exactly what they do, and what is required for them to reach full stability.
The catalog and scaffold commands now support configurability in the root configuration include used for their scaffolding.
This allows users to use a root Terragrunt configuration named anything they like, and scaffold new units conveniently, pulling those configurations in with a simple CLI flag.
🛠️ Breaking Changes
The recent work introduced in #3562 to support symlinks has been downgraded to an experiment. We merged in this feature believing it had enough testing to be supported at launch, but quite a bit of unexpected regression occurred as a consequence.
If you are still using this functionality, use the
--experiment symlinks
flag to re-enable it in your environments. For more information, you can read the documentation on Controlling Experiment Mode.This release also deprecates one of the longest lasting patterns of Terragrunt usage, the root
terragrunt.hcl
file.To reiterate the note in the migration guide, this is not going to be a breaking change for a very long time, but we want to start encouraging users to adopt new patterns.
The practice of using
terragrunt.hcl
as the root of Terragrunt configurations has been harmful to new Terragrunt users and experienced users alike, and we want to have Terragrunt start communicating better practices.You will have ample warning before this functionality is no longer supported.
📖 Documentation Updates
The Features section of the docs has been revamped significantly to improve the ability to understand and use Terragrunt features at a glance. Much more will be done in the near future to improve the experience of using Terragrunt documentation, and your feedback is always actively solicited!
What's Changed
terragrunt.hcl
as root by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/3588ProviderCacheWithProviderCacheDir
test by @levkohimins in https://github.com/gruntwork-io/terragrunt/pull/3656Full Changelog: gruntwork-io/terragrunt@v0.69.13...v0.70.0
v0.69.13
Compare Source
What's Changed
New Contributors
Full Changelog: gruntwork-io/terragrunt@v0.69.12...v0.69.13
v0.69.12
Compare Source
What's Changed
endpoints.s3
inremote_state
block. by @wakeful in https://github.com/gruntwork-io/terragrunt/pull/3643Full Changelog: gruntwork-io/terragrunt@v0.69.11...v0.69.12
v0.69.11
Compare Source
What's Changed
New Contributors
Full Changelog: gruntwork-io/terragrunt@v0.69.10...v0.69.11
v0.69.10
Compare Source
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.69.9...v0.69.10
v0.69.9
Compare Source
Updated CLI args, config attributes and blocks
engine
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.69.8...v0.69.9
v0.69.8
Compare Source
Updated CLI args, config attributes and blocks
errors
What's Changed
error
block.error
block.Full Changelog: gruntwork-io/terragrunt@v0.69.7...v0.69.8
v0.69.7
Compare Source
New built-in function
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.69.6...v0.69.7
v0.69.6
Compare Source
Updated CLI args, config attributes and blocks
errors
New Feature:
errors
configuration blockThis release introduces an improved configuration block for managing errors, enhancing the flexibility of retry and ignore mechanisms. These new features provide fine-grained control over error handling, ensuring a smoother and more robust execution flow.
Example
Demo
Ignore error:
Retry error:
What's Changed
errors
blockRelated links
Full Changelog: gruntwork-io/terragrunt@v0.69.5...v0.69.6
v0.69.5
Compare Source
Updated CLI args, config attributes and blocks
New Flags
--terragrunt-hclfmt-exclude-dir
: Exclude directories from HCL formatting when using thehclfmt
command. For more, see the docs.What's Changed
--terragrunt-hclfmt-exclude-dir
parameter tohclfmt
command by @wakeful in https://github.com/gruntwork-io/terragrunt/pull/3609New Contributors
Full Changelog: gruntwork-io/terragrunt@v0.69.3...v0.69.5
v0.69.3
Compare Source
What's Changed
error_hook
processing only takesstderr
into account and ignoresstdout
TF output.trace
, e.g.--terragrunt-log-level trace
.Full Changelog: gruntwork-io/terragrunt@v0.69.2...v0.69.3
v0.69.2
Compare Source
Updated CLI args, config attributes and blocks
--terragrunt-tf-logs-to-json
DEPRECATED: Use terragrunt-log-formatBreaking Changes
stdout
andstderr
is wrapped in JSON by default with--terragurnt-log-format json
flag. In other words, the previous behavior with the--terragrunt-json-log --terragrunt-tf-logs-to-json
flags is now equivalent to--terragrunt-log-format json
and the previous behavior with the--terragrunt-json-log
is now equivalent to--terragrunt-log-format json --terragrunt-forward-tf-stdout
.--terragurnt-log-format json
and--terragurnt-log-format key-value
formats:tfpath
->tf-path
workingDir
->working-dir
executedCommandArgs
->tf-command-args
What's Changed
New Contributors
Full Changelog: gruntwork-io/terragrunt@v0.69.1...v0.69.2
v0.69.1
Compare Source
New Feature
Using the OpenTofu/Terraform -detailed-exitcode flag with the run-all command results in an aggregate exit code being returned, rather than the exit code of any particular unit.
The algorithm for determining the aggregate exit code is as follows:
If any unit throws a 1, Terragrunt will throw a 1.
If any unit throws a 2, but nothing throws a 1, Terragrunt will throw a 2.
If nothing throws a non-zero, Terragrunt will throw a 0.
What's Changed
-detailed-exitcode
withrun-all
commands by @levkohimins in https://github.com/gruntwork-io/terragrunt/pull/3585Full Changelog: gruntwork-io/terragrunt@v0.69.0...v0.69.1
v0.69.0
Compare Source
TFLint update
The internal version of TFLint has been updated from
v0.47.0
tov0.50.3
.Given that this might result in breakage for users with tflint hooks, this is being released as a new minor release.
What's Changed
v0.50.3
by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/3569Full Changelog: gruntwork-io/terragrunt@v0.68.17...v0.69.0
v0.68.17
Compare Source
Updated CLI args, config attributes and blocks
terraform
What's Changed
feature
andexclude
.Related links
Full Changelog: gruntwork-io/terragrunt@v0.68.16...v0.68.17
v0.68.16
Compare Source
Updated CLI args, config attributes and blocks
exclude
feature
New Feature:
exclude
configuration blockThe
exclude
configuration block allows for dynamic exclusion of units from the run queue, similar to the now deprecatedskip
attribute. Theexclude
configuration block allows for more control over exactly how units are excluded from the run queue, and integrates very well with thefeature
block introduced in v0.68.9.For more information, read the docs.
Example
Demo
What's Changed
exclude
block, enabling users to define more advanced and flexible criteria for excluding specific units, enhancing customization and control over unit selection processes.feature
blocksRenderJSONithMetadata
asRenderJSONWithMetadata
Related links
v0.68.15
Compare Source
Updated CLI args, config attributes and blocks
--terragrunt-log-format [ bare | pretty | json | key-value ]
--terragrunt-log-custom-format "%time %level %prefix %msg"
Feature Description
Using the
--terragrunt-log-custom-format <format>
flag you can customize the Terragrunt logs. Make sure to read Custom Log Format for syntax details.Examples
--terragrunt-log-format bare
--terragrunt-log-format key-value
--terragrunt-log-format json
--terragrunt-log-format pretty
--terragrunt-log-custom-format "%level(format=tiny,case=upper,color=preset) %interval %prefix(path=short-relative,color=gradient,suffix=' ')%msg(path=relative)"
"%time(format='H:m:s',color=yellow) %level(format=short,case=upper,color=preset) %prefix(color=gradient,suffix=' ',align=right)%msg(path=relative)"
--terragrunt-log-custom-format "%(content='time=',color=magenta)%time %(content='level=',color=light-blue)%level %(content='msg=',color=green)%msg"
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.68.14...v0.68.15
v0.68.14
Compare Source
Updated CLI args, config attributes and blocks
terragrunt-queue-include-units-reading
terragrunt-auth-provider-cmd
terragrunt-queue-include-units-reading
UpdatesThe
terragrunt-queue-include-units-reading
flag is now results in a super set of functionality provided by theterragrunt-modules-that-include
flag.Using either will include all units that include particular Terragrunt configurations, while the
terragrunt-queue-include-units-reading
will also add in files that are read by HCL functions.For more information (including limitations of the flag), read the docs.
terragrunt-auth-provider-cmd
UpdatesThe
terragrunt-auth-provider-cmd
flag is now capable of supporting AWS role assumptions in addition to supporting the setting of explicit AWS credentials, and generic environment variables.This allows users to configure Terragrunt to dynamically assume different AWS roles at runtime, depending on the context of the unit.
This support includes support for role assumption using the
AssumeRoleWithWebIdentity
API, which allows for dynamic assumption of OIDC roles in CI platforms like GitHub Actions, GitLab CI/CD and CircleCI.For more information, read the docs.
What's Changed
Full Changelog: gruntwork-io/terragrunt@v0.68.13...v0.68.14
[
v0.68.13
](https://redirect.github.com/gruntwork-iConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.