v0.5.4

🤖 Automatic Updates

chore(deps): update terraform cloudposse/s3-bucket/aws to v4.3.0 @renovate (#61)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	minor	4.2.0 -> 4.3.0

---

Release Notes

cloudposse/terraform-aws-s3-bucket (cloudposse/s3-bucket/aws)

v4.3.0

Compare Source

Enforce the usage of modern TLS versions (1.2 or higher) for S3 connections @​amontalban (#​237)

what

This variables adds a policy to the bucket to deny connections that do not use TLS 1.2 or higher.

why

This is required by our security team.

references

https://repost.aws/knowledge-center/s3-enforce-modern-tls

🚀 Enhancements

Bump github.com/hashicorp/go-getter from 1.7.1 to 1.7.4 in /test/src @​dependabot (#​230)

Bumps github.com/hashicorp/go-getter from 1.7.1 to 1.7.4.

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.4

What's Changed

• Escape user-provided strings in git commands hashicorp/go-getter#483
• Fixed a bug in .netrc handling if the file does not exist hashicorp/go-getter#433

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.3...v1.7.4

v1.7.3

What's Changed

• SEC-090: Automated trusted workflow pinning (2023-04-21) by @​​hashicorp-tsccr in hashicorp/go-getter#432
• SEC-090: Automated trusted workflow pinning (2023-09-11) by @​​hashicorp-tsccr in hashicorp/go-getter#454
• SEC-090: Automated trusted workflow pinning (2023-09-18) by @​​hashicorp-tsccr in hashicorp/go-getter#458
• don't change GIT_SSH_COMMAND when there is no sshKeyFile by @​​jbardin in hashicorp/go-getter#459

New Contributors

• @​​hashicorp-tsccr made their first contribution in hashicorp/go-getter#432

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.2...v1.7.3

v1.7.2

What's Changed

• Don't override GIT_SSH_COMMAND when not needed by @​​nl-brett-stime hashicorp/go-getter#300

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.1...v1.7.2

Commits

• 268c11c escape user provide string to git (#​483)
• 975961f Merge pull request #​433 from adrian-bl/netrc-fix
• 0298a22 Merge pull request #​459 from hashicorp/jbardin/setup-git-env
• c70d9c9 don't change GIT_SSH_COMMAND if there's no keyfile
• 3d5770f Merge pull request #​458 from hashicorp/tsccr-auto-pinning/trusted/2023-09-18
• 0688979 Result of tsccr-helper -log-level=info -pin-all-workflows .
• e66f244 Merge pull request #​454 from hashicorp/tsccr-auto-pinning/trusted/2023-09-11
• e80b3dc Result of tsccr-helper -log-level=info -pin-all-workflows .
• 2d49e24 Merge pull request #​432 from hashicorp/tsccr-auto-pinning/trusted/2023-04-21
• 5ccb39a Make addAuthFromNetrc ignore ENOTDIR errors
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

🤖 Automatic Updates

Bump github.com/hashicorp/go-getter from 1.7.1 to 1.7.4 in /test/src @​dependabot (#​230)

Bumps github.com/hashicorp/go-getter from 1.7.1 to 1.7.4.

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.4

What's Changed

• Escape user-provided strings in git commands hashicorp/go-getter#483
• Fixed a bug in .netrc handling if the file does not exist hashicorp/go-getter#433

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.3...v1.7.4

v1.7.3

What's Changed

v0.5.3

🤖 Automatic Updates

chore(deps): update terraform cloudposse/s3-bucket/aws to v4.2.0 @renovate (#43)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	minor	4.0.1 -> 4.2.0

---

Release Notes

cloudposse/terraform-aws-s3-bucket (cloudposse/s3-bucket/aws)

v4.2.0

Compare Source

Added IP-based statement in bucket policy @​soya-miyoshi (#​216)

what

• Allows users to specify a list of source IP addresses from which access to the S3 bucket is allowed.
• Adds dynamic statement that uses the NotIpAddress condition to deny access from any IP address not listed in the source_ip_allow_list variable.

why

Use cases:

• Restricting access to specific physical locations, such as an office or home network

references

v4.1.0

Compare Source

🚀 Enhancements

fix: use for_each instead of count in aws_s3_bucket_logging @​wadhah101 (#​212)

what

Replaced the count with a for_each inside aws_s3_bucket_logging.default

there's no point in the try since the type is clearly defined as list

why

When the bucket_name within logging attribute is dynamically defined, like in the case of referencing a bucket created by terraform for logging

  logging = [
    {
      bucket_name = module.logging_bucket.bucket_id
      prefix      = "data/"
    }
  ]

we get this error

For each can work better in this case and will solve the previous error

references

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​214)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update README.md and docs @​cloudpossebot (#​213)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update README.md and docs @​cloudpossebot (#​209)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

---

v0.6.0

🤖 Automatic Updates

chore(deps): update terraform cloudposse/s3-bucket/aws to v4 @renovate (#40)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	major	3.1.3 -> 4.0.1

---

Release Notes

cloudposse/terraform-aws-s3-bucket (cloudposse/s3-bucket/aws)

v4.0.1

Compare Source

🐛 Bug Fixes

Fix bug in setting dynamic `encryption_configuration` value @​LawrenceWarren (#​206)

what

• When trying to create an S3 bucket, the following error is encountered:

Error: Invalid dynamic for_each value

  on .terraform/main.tf line 225, in resource "aws_s3_bucket_replication_configuration" "default":
 225:           for_each = try(compact(concat(
 226:             [try(rule.value.destination.encryption_configuration.replica_kms_key_id, "")],
 227:             [try(rule.value.destination.replica_kms_key_id, "")]
 228:           ))[0], [])
    ├────────────────
    │ rule.value.destination.encryption_configuration is null
    │ rule.value.destination.replica_kms_key_id is "arn:aws:kms:my-region:my-account-id:my-key-alias"

Cannot use a string value in for_each. An iterable collection is required.

• This is caused in my case by having s3_replication_rules.destination.encryption_configuration.replica_kms_key_id set.

why

• There is a bug when trying to create an S3 bucket, which causes an error that stops the bucket being created

  • Basically, there are two attributes that do the same thing (for backwards compatability)
    • s3_replication_rules.destination.encryption_configuration.replica_kms_key_id (newer)
    • s3_replication_rules.destination.replica_kms_key_id (older)
  • There is logic to:
    • A) use the newer of these two attributes
    • B) fall back to the older of the attributes if it is set and the newer is not
    • C) fall back to an empty array if nothing is set
  • There is a bug in steps A/B, where by selecting one or the other, we end up with the string value, and not an iterable
  • The simplest solution, which I have tested successfully on existing buckets, is to wrap the output of that logic in a list

• This error is easily replicable by trying compact(concat([try("string", "")], [try("string", "")]))[0] in the Terraform console, which is a simplified version of the existing logic used above

• The table below demonstrates the possible values of the existing code - you can see the outputs for value 2, value 3, and value 4 are not lists:

Key	Value 1	Value 2	Value 3	Value 4
newer	null	"string1"	null	"string1"
older	null	null	"string2"	"string2"
output	[]	"string1"	"string2"	"string1"

v4.0.0

Compare Source

Bug fixes and enhancements combined into a single breaking release @​aknysh (#​202)

Breaking Changes

Terraform version 1.3.0 or later is now required.

policy input removed

The deprecated policy input has been removed. Use source_policy_documents instead.

Convert from

policy = data.aws_iam_policy_document.log_delivery.json

to

source_policy_documents = [data.aws_iam_policy_document.log_delivery.json]

Do not use list modifiers like sort, compact, or distinct on the list, or it will trigger an Error: Invalid count argument. The length of the list must be known at plan time.

Logging configuration converted to list

To fix #​182, the logging input has been converted to a list. If you have a logging configuration, simply surround it with brackets.

Replication rules brought into alignment with Terraform resource

Previously, the s3_replication_rules input had some deviations from the aws_s3_bucket_replication_configuration Terraform resource. Via the use of optional attributes, the input now closely matches the resource while providing backward compatibility, with a few exceptions.

• Replication source_selection_criteria.sse_kms_encrypted_objects was documented as an object with one member, enabled, of type bool. However, it only worked when set to the string "Enabled". It has been replaced with the resource's choice of status of type String.
• Previously, Replication Time Control could not be set directly. It was implicitly enabled by enabling Replication Metrics. We preserve that behavior even though we now add a configuration block for replication_time. To enable Metrics without Replication Time Control, you must set replication_time.status = "Disabled".

These are not changes, just continued deviations from the resources:

• existing_object_replication cannot be set.
• token to allow replication to be enabled on an Object Lock-enabled bucket cannot be set.

what

• Remove local local.source_policy_documents and deprecated variable policy (because of that, pump the module to a major version)
• Convert lifecycle_configuration_rules and s3_replication_rules from loosely typed objects to fully typed objects with optional attributes.
• Use local bucket_id variable
• Remove comments suppressing Bridgecrew rules
• Update tests to Golang 1.20

why

• The number of policy documents needs to be known at plan time. Default value of policy was empty, meaning it had to be removed based on content, which would not be known at plan time if the policy input was being generated.
• Closes #​167, supersedes and closes #​163, and generally makes these inputs easier to deal with, since they now have type checking and partial defaults, meaning the inputs can be much smaller.
• Incorporates and closes #​197. Thank you @​nikpivkin
• Suppressing Bridgecrew rules Cloud Posse does not like should be done via external configuration so that users of this module can have the option of having those rules enforced.
• Security and bug fixes

explanation

Any list manipulation functions should not be used in count since it can lead to the error:

│ Error: Invalid count argument
│
│   on ./modules/s3_bucket/main.tf line 462, in resource "aws_s3_bucket_policy" "default":
│  462:   count      = local.enabled && (var.allow_ssl_requests_only || var.allow_encrypted_uploads_only || length(var.s3_replication_source_roles) > 0 || length(var.privileged_principal_arns) > 0 || length(local.source_policy_documents) > 0) ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined until apply, so Terraform cannot predict how many instances will be created. To work around this, use the -target argument to
│ first apply only the resources that the count depends on.

Using the local like this

source_policy_documents = var.policy != "" && var.policy != null ? concat([var.policy], var.source_policy_documents) : var.source_policy_documents

would not work either if var.policy depends on apply-time resources from other TF modules.

General rules:

• When using for_each, the map keys have to be known at plan time (the map values are not required to be know at plan time)

• When using count, the length of the list must be know at plan time, the items inside the list are not. That does not mean that the list must be static with the length known in advance, the list can be dynamic and come from a remote state or data sources which Terraform evaluates first during plan, it just can’t come from other resources (which are only known after apply)

• When using count, no list manipulating functions can be used in count - it will lead to the The "count" value depends on resource attributes that cannot be determined until apply error in some cases

---

v0.5.1

🤖 Automatic Updates

chore(deps): update terraform cloudposse/s3-bucket/aws to v3.1.3 @renovate (#39)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	3.1.2 -> 3.1.3

---

Release Notes

cloudposse/terraform-aws-s3-bucket (cloudposse/s3-bucket/aws)

v3.1.3

Compare Source

Unfortunately, this change makes count unknown at plan time in certain situations. In general, you cannot use the output of compact() in count.

The solution is to stop using the deprecated policy input and revert to 3.1.2 or upgrade to 4.0.

🚀 Enhancements

Fix `source_policy_documents` combined with `var.policy` being ignored @​johncblandii (#​201)

what

• Changed var.source_policy_documents to local.source_policy_documents so var.policy usage was still supported

why

• The ternary check uses var,source_policy_documents so var.policy being combined with var.source_policy_documents into local.source_policy_documents does not provide true for the ternary to execute

references

• https://github.com/cloudposse/terraform-aws-config-storage/pull/39

---

chore(deps): update terraform cloudposse/vpc/aws to v2.1.1 @renovate (#42)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/vpc/aws (source)	module	patch	2.1.0 -> 2.1.1

---

Release Notes

cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)

v2.1.1

Compare Source

Add support for network address usage metrics @​lanzrein (#​124)

what

This PR adds support for Network Address Usage Metrics on the VPC.
AWS documentation : https://docs.aws.amazon.com/vpc/latest/userguide/network-address-usage.html
Terraform documentation : https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc#enable_network_address_usage_metrics

why

Network Address Usage metrics can help monitor the growth of a VPC and would be useful for any user.
Enable this after creating a VPC does not trigger recreation of the VPC.

references

closes #​115

Sync github @​max-lobur (#​120)

Rebuild github dir from the template

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​125)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

---

Update README.md and docs @cloudpossebot (#41)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.5.0

(firewall-manager-shield_advanced): add missing attributes @eladlevi-dy (#38)

add missing attribues that cause drifts.

add attributes automaticResponseStatus, automaticResponseAction and overrideCustomerWebaclClassic.

why

These attributes are part of the firewall manager shield advanced policy values and had to be addressed in the module, otherwise there will be drift any time "drift detection" runs.

      ~ security_service_policy_data {
          ~ managed_service_data = jsonencode(
              ~ {
                  - automaticResponseConfiguration = {
                      - automaticResponseAction = null
                      - automaticResponseStatus = "IGNORED"
                    } -> null
                  - overrideCustomerWebaclClassic  = false -> null
                    # (1 unchanged element hidden)
                }
            )
            # (1 unchanged attribute hidden)
        }
        # (2 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

references

Link to AWS doc.

v0.4.1

feat(firewall-manager-waf_v2): add missing attributes @eladlevi-dy (#36)

add missing attribues that cause drifts.

• add attributes customRequestHandling, customResponse and sampledRequestsEnabledForDefaultActions.

why

• These attributes are part of the firewall manager wafv2 policy values and had to be addressed in the module, otherwise there will be drift any time "drift detection" runs.

      ~ security_service_policy_data {
          ~ managed_service_data = jsonencode(
              ~ {
                  - customRequestHandling                   = null -> null
                  - customResponse                          = null -> null
                  - sampledRequestsEnabledForDefaultActions = null -> null
                    # (6 unchanged elements hidden)
                }
            )
            # (1 unchanged attribute hidden)
        }
        # (2 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

references

Link to AWS API_SecurityServicePolicyData

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#30)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.4.0

Update shield_advanced.tf @eladlevi-dy (#28)

Add the option to use "delete_unused_fm_managed_resources" on shield_advanced.

what

• Terraform resource "aws_fms_policy" has the optional "delete_unused_fm_managed_resources" argument but the module does not.
• delete_unused_fm_managed_resources - (Optional) If true, Firewall Manager will automatically remove protections from resources that leave the policy scope. Defaults to false.

why

This change is needed because if resource is out of scope we don't want to keep using shield and gain extra unneeded costs

references

hashicorp - Terraform

Fix Example Code @milldr (#29)

what

• Fixed a typo with shield_advanced_policies
• Bumped the vpc module version
• Bumped s3-bucket module version
• Updated deprecated inputs for kinesis_firehose_delivery_stream
• Fixed tflint updated recommendations

why

• This example is broken and is causing tests to fail in other PRs

references

• #28
• closes #18
• closes #21
• closes #24
• closes #20

Sync github @max-lobur (#25)

Rebuild github dir from the template

git.io->cloudposse.tools update @dylanbannon (#22)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

v0.3.0 Breaking: shiled_advanced_policies renamed shield_advanced_policies

Breaking change

• shiled_advanced_policies renamed shield_advanced_policies

Fix default values, typo @Nuru (#17)

Special Note

This PR is a duplicate of #10, which was authored by @lgallard. See that PR for details. This PR replaces #10 due to administrative/permissions issues only. Supersedes and closes #10.

what

• Change default values to include_map and exclude_map attributes
• Fix typo: shiled -> shield

why

• To avoid different types in Terraform conditionals
• Fix typo in naming resources.

references

• closes #5
• closes #15

v0.2.5

🤖 Automatic Updates

chore(deps): update terraform cloudposse/s3-bucket/aws to v0.44.1 @renovate (#13)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	minor	0.38.0 -> 0.44.1

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v0.44.1

Compare Source

🚀 Enhancements

Dynamic block for versioning added @​nnsense (#​118)

##### what Enabling `versioning` on a bucket is a permanent action that cannot be disabled. For this reason, when `versioning` attribute is added to the s3 resource, the bucket is prepared to be `versioned` and put in suspended mode. The only way to avoid this and keep the versioning disabled is to not add the `versioning` attribute at all.

We were discussing this in this bug and @​aknysh posted a snipped which is removing the attribute, making it possible to set versioning off instead of enabled but suspended.

I'm just adding that snippet, there's another PR which is apparently changing more than just the versioning and it seems abandoned (opened in February 2021, had no updates from August).

Note: there's a comment into this module's main:

#bridgecrew:skip=BC_AWS_S3_16:Skipping `Ensure S3 bucket versioning is enabled` because dynamic blocks are not supported by checkov

But I see that some basic handling for dynamic blocks has been added in checkov
bridgecrewio/checkov#​836

So if you're using checkov it would be interesting to remove the comment and see if it works now

why

• In a very quick deployment, where versioning is less important than speed, having a delay before an object can be written could be an issue (See the note here)
• If the buckets are created by terraform and deleted by a script, the versioned bucket's deletion is much more complex than a non-versioned one.
• User's preference

v0.44.0

Compare Source

Allow specifying aws_s3_bucket_ownership_controls @​max-lobur (#​109)

##### what * Allow setting aws_s3_bucket_ownership_controls ##### why * Per [docs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html) this setting will let object uploader decide ownership. If `bucket-owner-full-control` ACL is specified, the bucket account take ownership, otherwise the writer account keeps ownership. Bucket on its side may enforce presence of the `bucket-owner-full-control` ACL which we already do when needed. So this setting was the only missing piece to make ownership work like we expected * I found no use cases for the other value of this resource: `ObjectWriter`. It corresponds to legacy S3 behavior which was broken for us. * However, giving the broad use of this module, I suspect there might be use cases that rely on previous S3 behavior: They set the ACL `bucket-owner-full-control` in their request and then still expect to own the object. To preserve legacy behavior I made this a variable, and the default corresponds to S3 legacy behavior. This is a new feature of AWS and we should wait for some time before enforcing the new default. ##### references * https://aws.amazon.com/blogs/storage/enforcing-ownership-of-amazon-s3-objects-in-a-multi-account-environment/ * https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html * https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_ownership_controls#ObjectWriter

v0.43.4

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/iam-s3-user/aws to v0.15.7 @​renovate (#​113)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/iam-s3-user/aws (source)	module	patch	0.15.6 -> 0.15.7

---

Release Notes

cloudposse/terraform-aws-iam-s3-user

##### [`v0.15.7`](https://togithub.com/cloudposse/terraform-aws-iam-s3-user/releases/0.15.7)

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/iam-system-user/aws to v0.22.5 @​&#​8203;renovate (#&#​8203;39)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/iam-system-user/aws (source)	module	patch	0.22.4 -> 0.22.5

---

Release Notes

cloudposse/terraform-aws-iam-system-user

##### [`v0.22.5`](https://togithub.com/cloudposse/terraform-aws-iam-system-user/releases/0.22.5)

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/ssm-parameter-store/aws to v0.8.3 @​&#​8203;&#&#​8203;8203;renovate (#&#&#​8203;8203;57)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ssm-parameter-store/aws (source)	module	patch	0.8.2 -> 0.8.3

---

Release Notes

cloudposse/terraform-aws-ssm-parameter-store

##### [`v0.8.3`](https://togithub.com/cloudposse/terraform-aws-ssm-parameter-store/releases/0.8.3)

Compare Source

🚀 Enhancements

feat: Template provider removed from versions.tf @​&#​8203;&#&#​8203;8203;&#&#&#​8203;8203;8203;DovnarAlexander (#&#&#&#​8203;8203;8203;36)

##### what * Template provider removed from versions.tf ##### why * This provider is not used and deprecated. On ARM platforms Terraform raises an exception (because it does not have a build for it) ##### references * https://registry.terraform.io/providers/hashicorp/template/latest/docs

---

Configuration

📅 Schedule: At any time (no schedule defined).

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

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

v0.43.3

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/iam-s3-user/aws to v0.15.6 @​renovate (#​112)

This PR contains the following updates:

Package	Type	Update	Change
[cloudposse/iam-s3-user/aws](https://registry.terraform.io/modules/cloudposse/iam-s3-user/aw...

v0.2.4

🤖 Automatic Updates

Update context.tf @cloudpossebot (#16)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.