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(deps): update all dependencies #197

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

platform-engineering-bot
Copy link
Contributor

@platform-engineering-bot platform-engineering-bot commented Nov 25, 2024

This PR contains the following updates:

Package Type Update Change
ansible (source) major ==10.6.0 -> ==11.1.0
awscli minor 2.21.3 -> 2.22.20
docker/build-push-action action minor v6.9.0 -> v6.10.0
docker/metadata-action action minor v5.5.1 -> v5.6.1
pulumi minor 3.139.0 -> 3.143.0
terraform minor 1.9.8 -> 1.10.3
terragrunt minor 0.68.14 -> 0.70.4

Release Notes

ansible-community/ansible-build-data (ansible)

v11.1.0

Compare Source

v11.0.0

Compare Source

v10.7.0

Compare Source

aws/aws-cli (awscli)

v2.22.20

Compare Source

v2.22.19

Compare Source

v2.22.18

Compare Source

v2.22.17

Compare Source

v2.22.16

Compare Source

v2.22.15

Compare Source

v2.22.14

Compare Source

v2.22.13

Compare Source

v2.22.12

Compare Source

v2.22.11

Compare Source

v2.22.10

Compare Source

v2.22.9

Compare Source

v2.22.8

Compare Source

v2.22.7

Compare Source

v2.22.6

Compare Source

v2.22.5

Compare Source

v2.22.4

Compare Source

v2.22.3

Compare Source

v2.22.2

Compare Source

v2.22.1

Compare Source

v2.22.0

Compare Source

docker/build-push-action (docker/build-push-action)

v6.10.0

Compare Source

Full Changelog: docker/build-push-action@v6.9.0...v6.10.0

docker/metadata-action (docker/metadata-action)

v5.6.1

Compare Source

Full Changelog: docker/metadata-action@v5.6.0...v5.6.1

v5.6.0

Compare Source

Full Changelog: docker/metadata-action@v5.5.1...v5.6.0

pulumi/pulumi (pulumi)

v3.143.0

Compare Source

Features
  • [cli] Autonaming configuration in experimental mode
    #​17916

  • [cli] Suggest state repair as part of integrity panics
    #​17919

  • [engine] Add PULUMI_DEBUG_LANGUAGES much like PULUMI_DEBUG_PROVIDERS so we can attach debuggers to languages easily
    #​17821

  • [engine] Warn if refresh or destroy use older plugins
    #​12196

  • [protobuf] Add Handshake to the provider protocol
    #​17819

  • [sdk/dotnet] Upgrade pulumi-dotnet to 3.71.0
    #​17937

  • [sdkgen/dotnet] Codegen for .NET InvokeOutputOptions
    #​17890

  • [programgen/{dotnet,nodejs,python}] Emit deferred outputs for mutually dependant components
    #​17859

  • [sdk/go] Allow specifying dependencies for output invokes. Go code generation for Output form invokes will use the new Context.InvokeOutput method.
    #​17791

  • [sdk/nodejs] Add getSchema to Provider interface
    #​17950

  • [sdk/{nodejs,python}] Update Python and NodeJS to use the new GetRequiredPackage functionality
    #​17910

  • [cli/package] Automatically set up package dependencies when adding a package when possible
    #​17815

  • [sdk/python] Drop Python 3.8 support
    #​17883

Bug Fixes
  • [backend/diy] Show a more correct URL for lock files in error messages
    #​17961

  • [sdk/go] Inherit protect from parents in the Go SDK
    #​17936

  • [sdk/go] Fix a defer leak when writing memory profiles
    #​17581

  • [sdk/go] Return when rejecting the InvokeOutput output on error
    #​18010

  • [sdkgen/go] Fix writing of go.mod files for parameterized packages
    #​17923

  • [auto/{go,nodejs,python}] Expose whoami token information in automation API types
    #​17735

  • [cli/install] Don't recreate virtualenvs when using venv
    #​17892

  • [auto/nodejs] Don't hang indefinitely on failed inputs
    #​17899

  • [auto/python] Catch BaseException in automation API server
    #​17909

  • [sdk/nodejs] Throw from output() on circular structures
    #​17852

  • [sdkgen/{nodejs,python}] Bump the minimum SDK version to 3.142.0
    #​17997

Miscellaneous
  • [pkg] Upgrade pulumi-java to v0.19.0
    #​18014

  • [sdk/python] Switch to ruff for linting and formatting
    #​17882

  • [sdkgen] Include parameterization details in pulumi-plugin.json
    #​17867

v3.142.0

Compare Source

Features
  • [cli] Reduce binary size by stripping debug information
    #​17868

  • [sdk/go] Add OutputWithDependencies
    #​17856

  • [sdk/java] Bump pulumi-java to 0.18.0

Bug Fixes
  • [cli] Fix login --interactive when no accounts are in the credentials file
    #​17860

  • [cli/new] Fix new to work with local template directories again
    #​17866

  • [sdkgen/dotnet] Fix parameterized packages to have version.txt
    #​17851

  • [sdk/python] uv toolchain: preserve env-vars when executing uv command
    #​17849

v3.141.0

Compare Source

Features
  • [sdk/dotnet] Update dotnet to 3.69.0
    #​17828

  • [cli/new] Allow URLs without a scheme for downloading templates
    #​17824

  • [sdk/nodejs] Allow specifiying additional dependencies for output invokes
    #​17632

  • [sdk/{nodejs,python}] Implement deferred output for nodejs and python
    #​17793

  • [sdk/python] Allow specifiying dependencies for output invokes
    #​17751

  • [sdk/yaml] Update yaml to 1.12.0
    #​17811

Bug Fixes
  • [engine] Send the same program arguments to shimless and binary plugins
    #​17833

  • [auto/go] Work around a race where the summary event in the automation API sometimes cannot be found
    #​17825

  • [sdk/nodejs] Fix mocks when multiple versions of @​pulumi/pulumi are loaded in a project
    #​17769

Miscellaneous
  • [sdk/go] Split public and internal representation of InvokeOptions
    #​17818

v3.140.0

Compare Source

Features
  • [pkg] Reject schemas with duplicate paths across resources and functions
    #​17797

  • [auto/go] Add --config-file functionality to Go Automation API preview, update, refresh, and destroy
    #​17774

Bug Fixes
  • [cli/plugin] Workaround for escape codes in output from .NET 9
    #​17783

  • [sdk/python] Fix merging InvokeOptions.version
    #​17750

hashicorp/terraform (terraform)

v1.10.3

Compare Source

1.10.3 (December 18, 2024)

BUG FIXES:

  • Terraform could panic when encountering an error during plan encoding (#​36212)

v1.10.2

Compare Source

1.10.2 (December 11, 2024)

BUG FIXES:

  • cli: variables in an auto-loaded tfvars file which were overridden during plan incorrectly show as changed during apply [GH-36180]

v1.10.1

Compare Source

1.10.1 (December 4, 2024)

BUG FIXES:

  • cli: Complex variables values set via environment variables were parsed incorrectly during apply (#​36121)
  • config: templatefile would panic if given and entirely unknown map of variables (#​36118)
  • config: templatefile would panic if the variables map contains marked values (#​36127)
  • config: Remove constraint that an expanded resource block must only be used in conjunction with imports using for_each (#​36119)
  • backend/s3: Lock files could not be written to buckets with object locking enabled (#​36120)

v1.10.0

Compare Source

1.10.0 (November 27, 2024)

NEW FEATURES:

  • Ephemeral resources: Ephemeral resources are read anew during each phase of Terraform evaluation, and cannot be persisted to state storage. Ephemeral resources always produce ephemeral values.
  • Ephemeral values: Input variables and outputs can now be defined as ephemeral. Ephemeral values may only be used in certain contexts in Terraform configuration, and are not persisted to the plan or state files.
    • ephemeralasnull function: a function takes a value of any type and returns a similar value of the same type with any ephemeral values replaced with non-ephemeral null values and all non-ephemeral values preserved.

BUG FIXES:

  • The secret_suffix in the kubernetes backend now includes validation to prevent errors when the secret_suffix ends with a number (#​35666).
  • The error message for an invalid default value for an input variable now indicates when the problem is with a nested value in a complex data type. (#​35465)
  • Sensitive marks could be incorrectly transferred to nested resource values, causing erroneous changes during a plan (#​35501)
  • Allow unknown error_message values to pass the core validate step, so variable validation can be completed later during plan
    (#​35537)
  • Unencoded slashes within GitHub module source refs were being truncated and incorrectly used as subdirectories in the request path (#​35552)
  • Terraform refresh-only plans with output only changes are now applyable. (#​35812)
  • Postconditions referencing self with many instances could encounter an error during evaluation (#​35895)
  • The plantimestamp() function would return an invalid date during validation (#​35902)
  • Updates to resources which were forced to use create_before_destroy could lose that flag in the state temporarily and cause cycles if immediately removed from the configuration (#​35966)
  • backend/cloud: Prefer KV tags, even when tags are defined as set (#​35937)
  • Simplify config generation (plan -generate-config-out) for string attributes that contain primitive types (e.g. numbers or booleans) (#​35984)
  • config: issensitive could incorrectly assert that an unknown value was not sensitive during plan, but later became sensitive during apply, causing failures where changes did not match the planned result (#​36012)
  • config: The evaluation of conditional expressions and for expression in HCL could lose marks with certain combinations of unknown values (#​36017)

ENHANCEMENTS:

  • The element function now accepts negative indices (#​35501)
  • Import block validation has been improved to provide more useful errors and catch more invalid cases during terraform validate (#​35543)
  • Performance enhancements for resource evaluation, especially when large numbers of resource instances are involved (#​35558)
  • The plan, apply, and refresh commands now produce a deprecated warning when using the -state flag. Instead use the path attribute within the local backend to modify the state file. (#​35660)
  • backend/cos: Add new auth for Tencent Cloud backend (#​35888)

UPGRADE NOTES:

  • backend/s3: Removes deprecated attributes for assuming IAM role. Must use the assume_role block (#​35721)
  • backend/s3: The s3 backend now supports S3 native state locking. When used with DynamoDB-based locking, locks will be acquired from both sources. In a future minor release of Terraform the DynamoDB locking mechanism and associated arguments will be deprecated. (#​35661)
  • moved: Moved blocks now respect reserved keywords when parsing resource addresses. Configurations that reference resources with type names that match top level blocks and keywords from moved blocks will need to prepend the resource. identifier to these references. (#​35850)
  • config: In order to ensure consistency in results from HCL conditional expressions, marks must be combined from all values within the expression to avoid losing mark information. This typically improves accuracy when validating configuration, but users may see sensitive results where they were lost previously.

Previous Releases

For information on prior major and minor releases, refer to their changelogs:

gruntwork-io/terragrunt (terragrunt)

v0.70.4

Compare Source

What's Changed

Full 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

Full 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.

⚠️ Deprecations

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

Full 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

Full 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

  • chore: enhanced engine extraction - switched to using the internal library for archive extraction, resulting in resolving CVEs
  • build(dep): bump github.com/creack/pty from 1.1.17 to 1.1.24
  • build(dep): bump github.com/charmbracelet/bubbles from 0.16.1 to 0.20.0

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

  • feat: Enhanced support for handling negative error patterns in the error block.
  • fix: Resolved broken links in the documentation.
  • chore: Updated documentation to clarify the priority of error evaluation within the 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 block

This 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
errors {

### Retry block for transient errors
    retry "retry_network" {
        retryable_errors = [".*Error: network timeout.*"]
        max_attempts = 3
        sleep_interval_sec = 5
    }

### Ignore block for non-critical errors
    ignore "ignore_warnings" {
        ignorable_errors = [
            ".*Warning: non-critical issue.*"
        ]
        message = "Ignoring non-critical warnings"
    }
}
Demo

Ignore error:

ignore-error

Retry error:

retry-on-error

What's Changed

  • Added errors block

Related 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 the hclfmt command. For more, see the docs.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.69.3...v0.69.5

v0.69.3

Compare Source

What's Changed

  • Fixing an issue when error_hook processing only takes stderr into account and ignores stdout TF output.
  • Displaying stack trace only at log level 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

Breaking Changes

  • OpenTofu/Terraform stdout and stderr 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.
  • Renaming log keys in --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

Full 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 to v0.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

Full 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

  • feat: Introduced support for detecting and handling symlinked modules, ensuring seamless module discovery.
  • docs: Quick start documentation update.
  • docs: Improved documentation for feature and exclude.

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 block

The exclude configuration block allows for dynamic exclusion of units from the run queue, similar to the now deprecated skip attribute. The exclude configuration block allows for more control over exactly how units are excluded from the run queue, and integrates very well with the feature block introduced in v0.68.9.

For more information, read the docs.

Example
### Exclude configurations allowing for dynamically determining when and how to exclude execution of nodes in the Terragrunt graph
exclude {
    if = feature.feature_name.value # Boolean expression that determines if the node should be excluded.
    actions = ["all"] # Actions to exclude when active. Other options might be ["plan", "apply", "all_except_output"], etc
    exclude_dependencies = feature.feature_name.value # Exclude dependencies of the node as well
}
Demo

tg-flags-exclude

What's Changed

  • feat: Introduced a new exclude block, enabling users to define more advanced and flexible criteria for excluding specific units, enhancing customization and control over unit selection processes.
  • fix: Fixed handling of empty feature blocks
  • fix: Fix spelling of RenderJSONithMetadata as RenderJSONWithMetadata

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

1  tmuxinator local 2024-11-19 at 11 09 30 AM

--terragrunt-log-format key-value

1  tmuxinator local 2024-11-19 at 11 10 05 AM

--terragrunt-log-format json

1  tmuxinator local 2024-11-19 at 11 10 55 AM

--terragrunt-log-format pretty

1  tmuxinator local 2024-11-19 at 11 11 22 AM

--terragrunt-log-custom-format "%level(format=tiny,case=upper,color=preset) %interval %prefix(path=short-relative,color=gradient,suffix=' ')%msg(path=relative)"

1  tmuxinator local 2024-11-19 at 11 19 18 AM

"%time(format='H:m:s',color=yellow) %level(format=short,case=upper,color=preset) %prefix(color=gradient,suffix=' ',align=right)%msg(path=relative)"

1  tmuxinator local 2024-11-19 at 11 27 51 AM

--terragrunt-log-custom-format "%(content='time=',color=magenta)%time %(content='level=',color=light-blue)%level %(content='msg=',color=green)%msg"

1  tmuxinator local 2024-11-19 at 11 41 33 AM

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.68.14...v0.68.15


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@platform-engineering-bot platform-engineering-bot force-pushed the renovate/all branch 10 times, most recently from 82ccc97 to f90ba63 Compare December 2, 2024 00:14
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/all branch 13 times, most recently from 20536d8 to 4680754 Compare December 9, 2024 00:14
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/all branch 7 times, most recently from a588079 to c454875 Compare December 12, 2024 19:24
@platform-engineering-bot platform-engineering-bot force-pushed the renovate/all branch 13 times, most recently from 6ef3c95 to a602143 Compare December 18, 2024 23:24
Signed-off-by: Platform Engineering Bot <[email protected]>
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.

1 participant