chore(deps): bump1 prd

[sajidk1]

This PR contains the following updates:

Package	Type	Update	Change
github.com/cloudposse/terraform-null-label	github	patch	0.24.0 -> 0.24.1
gruntwork-io/terragrunt		minor	0.28.18 -> 0.31.3
hashicorp/terraform		patch	1.0.1 -> 1.0.4

---

Release Notes

cloudposse/terraform-null-label

v0.24.1

Compare Source

Allow control of letter case of outputs @​SweetOps (#​107)

You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

• You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
• You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

Include updates to exports/context.tf @​Nuru (#​122 and #​123)

#### what - Include updates to `exports/context.tf` - Update README with features and compatibilty - Add validation for `id_length_limit` #### why - The `exports/context.tf` is what gets distributed and needs to be in sync - Replace outdated information - Was not validated earlier because validators are not supported in TF 0.12 but now we are dropping support for TF 0.12 and so we can add validators

Restore backward compatibility with v0.22.1 and earlier @​Nuru (#​121)

#### what - Restore backward compatibility with v0.22.1 and earlier - Allow setting of `label_key_case` and `label_value_case` by vars, not just by context attributes. #### why - Allow interoperability of old and new modules - Normally, root modules make settings via individual variables, not by setting an entire context block.

Incorporates and closes #​120

gruntwork-io/terragrunt

v0.31.3

Compare Source

Updated CLI args, config attributes and blocks

• include [block]

Description

• Added deep merge strategy for include. Refer to the updated documentation for more information on what deep merge means.

Related links

• Deep merge strategy gruntwork-io/terragrunt#1759

v0.31.2

Compare Source

Updated CLI args, config attributes and blocks

• include [block]

Description

• Added new attribute to include: merge_strategy. merge_strategy indicates how the included parent config should be merged with the child config. Currently, this only supports no_merge and shallow. When omitted, the merge strategy defaults to shallow (the same strategy as previous versions).

Related links

• Introduce concept of merge strategy for includes gruntwork-io/terragrunt#1724

v0.31.1

Compare Source

Updated CLI args, config attributes and blocks

• CLI args

Description

• Addressed bug where plan file args were not always passed to the end of the arg list when calling terraform. Now terragrunt will check all the args and determine if an arg is a plan file (a filename that exists on disk and ends with extension tfplan), and if it is, feed it to the end of the args list.

Special thanks

• A special thank you to @​PertsevRoman for the fix!

Related links

• fix: Check planfile and put it in the end of an arguments list gruntwork-io/terragrunt#1740

v0.31.0

Compare Source

Description

• Terraform 1.0 support: We are now testing Terragrunt against Terraform 1.0 and is confirmed to be working.
• Terraform functions have been updated to the versions shipped with Terraform 0.15.3 (previously the functions were pulled in from Terraform 0.12.24). These may include backward incompatibilities. Refer to the terraform release notes for more information.

Related links

gruntwork-io/terragrunt#1726

v0.30.7

Compare Source

Updated CLI args, config attributes and blocks

• include [block]

Description

Fix bug where using an exposed include with local in the same expression did not work when referencing in locals blocks.

Related links

gruntwork-io/terragrunt#1727
gruntwork-io/terragrunt#1728

v0.30.6

Compare Source

Updated CLI args, config attributes and blocks

• remote_state [block]

Description

• Fix the way the remote_state block handles the AWS partition settings so that it works correctly with GovCloud.

Special thanks

• A special thank you to @​ryno75 for the fix!

Related links

• Resolves #1369 gruntwork-io/terragrunt#1718

v0.30.5

Compare Source

Updated CLI args, config attributes and blocks

• include [block]

Description

Fix bug where exposing include did not work when referencing in locals blocks.

Related links

gruntwork-io/terragrunt#1721
gruntwork-io/terragrunt#1723

v0.30.4

Compare Source

Updated CLI args, config attributes and blocks

• include [block]

Description

You can now access values from included config. E.g., if you want to access a local var region defined in the parent terragrunt config, you can reference include.locals.region in the child config.

Note that there are a few limitations/differences with read_terragrunt_config:

• include references do not include fetched dependencies. This will change in the future.
• include references are not automatically available. You must set the new expose attribute to true to access the included references.
• At the moment, you can only have a single include block in the child, and you can only include one level deep (no nested includes). This will change in the future.

(This is the first of several features that implement the Imports RFC)

Related links

gruntwork-io/terragrunt#1566
gruntwork-io/terragrunt#1716

v0.30.3

Compare Source

Updated CLI args, config attributes and blocks

• run-all [command]

Description

Improved error messaging when multiple errors are returned.

Special thanks

Special thanks to @​derom for their contribution!

Related links

gruntwork-io/terragrunt#1703

v0.30.2

Compare Source

Updated CLI args, config attributes and blocks

• aws-provider-patch (command)

Description

Improve error messages in aws-provider-patch when the json input is malformed.

Related links

gruntwork-io/terragrunt#1715

v0.30.1

Compare Source

Updated CLI args, config attributes and blocks

• hclfmt (command)

Description

Updated documentation and help text in hclfmt command to clarify that it works on all files with hcl extension, not just terragrunt.hcl.

Special thanks

Special thanks to @​edgarsandi for their contribution!

Related links

gruntwork-io/terragrunt#1713

v0.30.0

Compare Source

Updated CLI args, config attributes and blocks

• aws-provider-patch (command)

Description

aws-provider-patch now supports additional data types. Previously aws-provider-patch only supported patching strings, which made it impossible to patch provider attributes that are not strings (e.g., the allowed_account_ids attribute of the aws provider, which is list(string) type).

Note that to support this, the aws-provider-patch now expects attribute values to be json encoded when passed in. That means that you need to quote the values in order for it to work. For example, if you previously ran:

terragrunt aws-provider-patch --terragrunt-override-attr region=us-east-2

you need to update the call to:

terragrunt aws-provider-patch --terragrunt-override-attr 'region="us-east-2"'

Related links

gruntwork-io/terragrunt#1714
gruntwork-io/terragrunt#1709

v0.29.10

Compare Source

Updated CLI args, config attributes and blocks

• yamldecode (helper function)

Description

Fix bug where yamldecode is unable decode certain forms of yaml.

Special thanks

Special thanks to @​andreykaipov for the contribution!

Related links

gruntwork-io/terragrunt#1706

v0.29.9

Compare Source

Updated CLI args, config attributes and blocks

• --terragrunt-include-external-dependencies

Description

You can now configure the --terragrunt-include-external-dependencies setting via the environment variable TERRAGRUNT_INCLUDE_EXTERNAL_DEPENDENCIES.

Special thanks

Special thanks to @​elebertus for the contribution!

Related links

gruntwork-io/terragrunt#1548

v0.29.8

Compare Source

Updated CLI args, config attributes and blocks

• --terragrunt-debug

Description

You can now control the --terragrunt-debug flag using the TERRAGRUNT_DEBUG environment variable.

Related links

gruntwork-io/terragrunt#1698

v0.29.7

Compare Source

Updated CLI args, config attributes and blocks

• iam_role

Description

Fix a bug where Terragrunt would not properly assume the IAM role specified via the iam_role parameter if you were using AWS SSO.

Special thanks

Thank you to @​stevie- for the contribution!

Related links

• fix(aws_helper): make sure AWS SSO shared profiles are considered by default gruntwork-io/terragrunt#1689

v0.29.6

Compare Source

Updated CLI args, config attributes and blocks

• --help

Description

Update the usage text for Terragrunt to reflect that options should go after the command. There should be no impact on Terragrunt's behavior in this release.

Special thanks

Thank you to @​Tarasovych for the contribution!

Related links

• Update command usage gruntwork-io/terragrunt#1687

v0.29.5

Compare Source

Updated CLI args, config attributes and blocks

• --terragrunt-source-map [CLI Arg]

Description

You can now configure the Terragrunt source map option using the environment variable TERRAGRUNT_SOURCE_MAP. You can configure multiple mappings using comma separated value encoding. For example, the following configures three mappings:

github.com/org/modules.git=/local/path/to/modules,gitlab.com/org-lab/modules.git=/local/path/to/modules,bitbucket.org/bitorg/modules.git=/local/path/to/modules,gitlab.com/org-lab/modules.git=/local/path/to/modules

Related links

• Add support for setting terragrunt-source-map using env vars gruntwork-io/terragrunt#1676

v0.29.4

Compare Source

Updated CLI args, config attributes and blocks

• --terragrunt-iam-assume-role-duration [new CLI Arg]
• iam_assume_role_duration [new config]

Description

You can now use the new CLI arg and config setting to configure the duration for the IAM role from --terragrunt-iam-role.

Special thanks

Thank you to @​thehunt33r for the contribution!

Related links

• Add support for STS duration option gruntwork-io/terragrunt#1673

v0.29.3

Compare Source

Updated CLI args, config attributes and blocks

• --terragrunt-source-map [CLI Arg]

Description

This release introduces --terragrunt-source-map, which can be used to provide multiple mappings to translate terragrunt source URLs in the config with another path. See the documentation for more information.

Related links

• Implement --terragrunt-source-map gruntwork-io/terragrunt#1674

v0.29.2

Compare Source

Updated CLI args, config attributes and blocks

• get_aws_account_id [func]
• get_aws_caller_identity_arn [func]
• get_aws_caller_identity_user_id [func]

Description

• Fixes bug where the default credentials chain for the get_aws_** functions ignored the config file (~/.aws/config).

Related links

• Honor the shared config in the default session gruntwork-io/terragrunt#1663

v0.29.1

Compare Source

Updated CLI args, config attributes and blocks

• remote_state ; s3

Description

• Fixes bug where AWS profile based authentication was not fully honored when automatic s3 bucket creation was happening.

Related links

• remote_state backend S3 bucket parameters not set when using an assumed role profile gruntwork-io/terragrunt#1650
• Fix #1650: Make sure credentials for STS get caller identity uses the configuration parameters gruntwork-io/terragrunt#1654

v0.29.0

Compare Source

Updated CLI args, config attributes and blocks

• (none)

Description

• Update Terragrunt to work with Terraform 0.15. There are no code or behavior changes, but marking this release as incompatible because from this release onwards, we are only testing with Terraform 0.15 and up.

Related links

• Update to Terraform 0.15 gruntwork-io/terragrunt#1651

v0.28.24

Compare Source

Updated CLI args, config attributes and blocks

• skip_bucket_versioning

Description

• If skip_bucket_versioning is set to true, and you are using GCS as a backend, Terragrunt will not only not enable versioning automatically, but now it will also no longer try to check if versioning is enabled either.

Special thanks

• Thank you to @​davidalger for the fix!

Related links

• Only check if versioning is enabled on GCS bucket when skip_bucket_versioning is false gruntwork-io/terragrunt#1610

v0.28.23

Compare Source

Updated CLI args, config attributes and blocks

• get_terraform_commands_that_need_locking()

Description

• Remove init from the list of commands returned by get_terraform_commands_that_need_locking(), as init does not support locking, and as of Terraform 0.15, will exit with an error if you try to use the lock parameters with it.

Special thanks

• Thank you to @​grimm26 for the fix!

Related links

• Remove init from TERRAFORM_COMMANDS_NEED_LOCKING gruntwork-io/terragrunt#1642

v0.28.22

Compare Source

Updated CLI args, config attributes and blocks

• sops_decrypt_file()

Description

• Updated the versions of sops, aws-sdk-go, and vault libraries that we depend on. As a result, the sops_decrypt_file() function should now work with data encrypted via HashiCorp Vault.

Special thanks

• Thank you to @​teamfighter for the contribution!

Related links

• Added vault support for sops encryption mechanism gruntwork-io/terragrunt#1564

v0.28.21

Compare Source

Updated CLI args, config attributes and blocks

• get_original_terragrunt_dir() [NEW]
• generate
• remote_state

Description

• Added a new get_original_terragrunt_dir() helper, which returns the directory where the original Terragrunt configuration file (by default terragrunt.hcl) lives. This is primarily useful when one Terragrunt config is being read from another: e.g., if /terraform-code/terragrunt.hcl calls read_terragrunt_config("/foo/bar.hcl"), and within bar.hcl, you call get_original_terragrunt_dir(), you'll get back /terraform-code.
• Updated the generate and remote_state settings so that they can be set either as blocks or attributes. This makes it possible to, for example, read these settings from common.hcl using read_terragrunt_config and set them dynamically.

Related links

• Add new get_original_terragrunt_dir() helper gruntwork-io/terragrunt#1637
• Allow generate and remote_state to be set as attrs gruntwork-io/terragrunt#1639

v0.28.20

Compare Source

Updated CLI args, config attributes and blocks

• --terragrunt-strict-include

Description

• When you pass in --terragrunt-strict-include, Terragrunt will now only execute within the directories passed in via --terragrunt-include-dir. If you set --terragrunt-strict-include, but don't pass in any directories via --terragrunt-include-dir, then Terragrunt will exit without doing anything. This is arguably a backwards incompatible change, but this is the behavior the --terragrunt-strict-include flag was intended to have originally, and is less surprising, so we're treating this as a bug fix.

Special thanks

• Thank you to @​celestialorb for the contribution!

Related links

• Fixing behavior of --terragrunt-strict-include when no --terragrunt-include-dir flags are included gruntwork-io/terragrunt#1631

v0.28.19

Compare Source

Updated CLI args, config attributes and blocks

• retry_max_attempts [NEW]
• retry_sleep_interval_sec [NEW]

Description

• Updated Terragrunt's auto retry functionality so that you can now configure the number of retry attempts and the time between retries using the new config attributes retry_max_attempts and retry_sleep_interval_sec, respectively.
• Switch log level of terragrunt dependency fetching informational messages to debug.

Special thanks

• Thank you to @​andreykaipov for the contribution!

Related links

• Add configurable retries gruntwork-io/terragrunt#1632
• Switch log level of terragrunt dependency fetching informational messages gruntwork-io/terragrunt#1628

hashicorp/terraform

v1.0.4

Compare Source

1.0.4 (August 04, 2021)

BUG FIXES:

• backend/consul: Fix a bug where the state value may be too large for consul to accept (#​28838)
• cli: Fixed a crashing bug with some edge-cases when reporting syntax errors that happen to be reported at the position of a newline. (#​29048)

v1.0.3

Compare Source

1.0.3 (July 21, 2021)

ENHANCEMENTS

• terraform plan: The JSON logs (-json option) will now include resource_drift, showing changes detected outside of Terraform during the refresh step. (#​29072)
• core: The automatic provider installer will now accept providers that are recorded in their registry as using provider protocol version 6. (#​29153)
• backend/etcdv3: New argument max_request_bytes allows larger requests and for the client, to match the server request limit. (#​28078)

BUG FIXES:

• terraform plan: Will no longer panic when trying to render null maps. (#​29207)
• backend/pg: Prevent the creation of multiple workspaces with the same name. (#​29157)
• backend/oss: STS auth is now supported. (#​29167)
• config: Dynamic blocks with unknown for_each values were not being validated. Ensure block attributes are valid even when the block is unknown (#​29208)
• config: Unknown values in string templates could lose sensitivity, causing the planned change to be inaccurate (#​29208)

v1.0.2

Compare Source

1.0.2 (July 07, 2021)

BUG FIXES:

• terraform show: Fix crash when rendering JSON plan with sensitive values in state (#​29049)
• config: The floor and ceil functions no longer lower the precision of arguments to what would fit inside a 64-bit float, instead preserving precision in a similar way as most other arithmetic functions. (#​29110)
• config: The flatten function was incorrectly treating null values of an unknown type as if they were unknown values. Now it will treat them the same as any other non-list/non-tuple value, flattening them down into the result as-is. (#​29110)

---

Configuration

📅 Schedule: 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.

---

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

---

This PR has been generated by Renovate Bot.