v1.535.2

🤖 Automatic Updates

Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#32)

## 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

chore(deps): update terraform cloudposse/stack-config/yaml to v1.8.0 @[renovate[bot]](https://github.com/apps/renovate) (#6)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/stack-config/yaml (source)	module	minor	1.5.0 -> 1.8.0

---

Release Notes

cloudposse/terraform-yaml-stack-config (cloudposse/stack-config/yaml)

v1.8.0: [remote-state] Improve backend compatibility

Compare Source

Among other things detailed below, this release enables users to fix deprecation warnings like:

│ Warning: Deprecated Parameters
│ 
│   with module.account_map.data.terraform_remote_state.data_source[0],
│   on .terraform/modules/account_map/modules/remote-state/data-source.tf line 88, in data "terraform_remote_state" "data_source":
│   88: data "terraform_remote_state" "data_source" {
│ 
│ The following parameters have been deprecated. Replace them as follows:
│   * role_arn -> assume_role.role_arn

(cf. #​93 and #​96)

If you are receiving deprecation warnings from remote-state, they can now be resolved by updating your backend/remote_state_backend configuration to match the version of Terraform or Tofu you are using. For example, change

terraform:
  backend:
    s3:
      bucket: my-tfstate-bucket
      dynamodb_table: my-tfstate-lock-table
      role_arn: arn:aws:iam::123456789012:role/my-tfstate-access-role
  remote_state_backend:
    s3:
      role_arn: arn:aws:iam::123456789012:role/my-tfstate-access-read-only-role

to

terraform:
  backend:
    s3:
      bucket: my-tfstate-bucket
      dynamodb_table: my-tfstate-lock-table
      assume_role:
        role_arn: arn:aws:iam::123456789012:role/my-tfstate-access-role
  remote_state_backend:
    s3:
      assume_role:
        role_arn: arn:aws:iam::123456789012:role/my-tfstate-access-read-only-role

🚀 Enhancements

[remote-state] Improve backend compatibility @​Nuru (#​105)

what

• Improve remote-state backend compatibility

Rather than trying to parse the backend configuration, as a general rule we now just pass it through to the data source. This provides future-proof compatibility with all backends supported by Terraform and OpenTofu.

why

• This prevents the need for updates like #​99 to provide configuration for future S3 backends, while eliminating compatibility issues like #​102.
• This also eliminates deprecation warnings caused by forcing configuration to look a certain way.
• Now, users can manage their own remote state configuration to match their toolset.

references

• Closes #​102

v1.7.0: (not recommended)

Compare Source

feat: support for gcs backends @​burnzy (#​95)

what

Simple change to add support for GCS backends

why

Allows GCP users (users with gcs backends) to make use of this remote-state module for sharing data between components.

references

• https://developer.hashicorp.com/terraform/language/settings/backends/gcs
• https://atmos.tools/core-concepts/share-data/#using-remote-state

🚀 Enhancements

Support local backend @​Nuru (#​104)

what

• Support retrieving remote state from local backends
  • NOTE: Using relative paths in local backends is tricky, because the path needs to resolve to the same directory from the source root module directory as from the client root module directory.
• Fix Terratests
  • The spacelift test suite is broken, and we never previously required it to work, so it is now skipped
• Update test suite to use go v1.21 and update dependencies

why

• When running demos and tests, it is more convenient to use local backends
• Maintain some degree of testing
• Closes multiple dependabot PRs:
  • Supersedes and Closes #​82
  • Supersedes and Closes #​83
  • Supersedes and Closes #​84
  • Supersedes and Closes #​87
  • Supersedes and Closes #​88

🤖 Automatic Updates

Bump the go_modules group in /test/src with 5 updates @​dependabot (#​94)

Bumps the go_modules group in /test/src with 5 updates:

Package	From	To
github.com/hashicorp/go-getter	1.7.1	1.7.5
golang.org/x/crypto	0.1.0	0.17.0
golang.org/x/net	0.8.0	0.10.0
google.golang.org/grpc	1.51.0	1.56.3
google.golang.org/protobuf	1.28.1	1.30.0

Updates github.com/hashicorp/go-getter from 1.7.1 to 1.7.5

Release notes

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

v1.7.5

What's Changed

• Prevent Git Config Alteration on Git Update by @​​dduzgun-security in hashicorp/go-getter#497

New Contributors

• @​​dduzgun-security made their first contribution in hashicorp/go-getter#497

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

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

v1.535.1

Fix datadog provider configuration @goruha (#28)

## what * Replace relative path for datadog creds module with git reference to the component

why

• After we split monorepo we can not use relative paths for component references

Summary by CodeRabbit

• Chores
  • Updated the Datadog configuration to use a remote module from a specific GitHub repository version instead of a local path.

🤖 Automatic Updates

Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#31)

## 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 @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#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

chore(deps): update terraform cloudposse/ecs-alb-service-task/aws to v0.78.0 @[renovate[bot]](https://github.com/apps/renovate) (#3)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ecs-alb-service-task/aws (source)	module	minor	0.66.2 -> 0.78.0

---

Release Notes

cloudposse/terraform-aws-ecs-alb-service-task (cloudposse/ecs-alb-service-task/aws)

v0.78.0

Compare Source

feat: enable fault injection @​rkul (#​261)

what

New parameter enables fault injection and allows for fault injection requests to be accepted from the task's containers

why

New option available in AWS ECS Task Definition

references

https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_TaskDefinition.html#:~:text=enableFaultInjection
https://github.com/hashicorp/terraform-provider-aws/issues/41077
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ecs_task_definition#enable_fault_injection-1

v0.77.0

Compare Source

feat: add support for availability_zone_rebalancing in aws_ecs_service resource @​dmitrijn (#​256)

what

• Add availability_zone_rebalancing attribute for aws_ecs_service
• Update minimum AWS provider version to v5.77.

why

• Useful for ecs service rebalancing

references

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html#cfn-ecs-service-availabilityzonerebalancing
https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.77.0

v0.76.1

Compare Source

fix: redeployment_trigger: replace timestamp() with plantimestamp() @​mslipets (#​251)

REF: https://github.com/hashicorp/terraform-provider-aws/issues/28070

what

in attempt to fix apply time issues like #​28070,
replace usage of function timestamp() with plantimestamp()

why

provided function apparently works for use cases when redeploy_on_apply && force_new_deployment set to true

references

• https://github.com/hashicorp/terraform-provider-aws/issues/28070

fix: update Terratest assertions with AWS account @​RoseSecurity (#​252)

what

• Update AWS account to fix this error:

Error:     Not equal: 
                   expected: "arn:aws:ecs:us-east-2:126450723953:cluster/eg-test-ecs-alb-service-task-ezatqz"
                   actual  : "arn:aws:ecs:us-east-2:799847381734:cluster/eg-test-ecs-alb-service-task-ezatqz"

why

• Terratests are failing due to assertions not validating with the expected account ID

references

• Failing Job

🤖 Automatic Updates

Migrate new test account @​osterman (#​249)

what

• Update .github/settings.yml
• Update .github/chatops.yml files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

Update .github/settings.yml @​osterman (#​248)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @​osterman (#​247)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

v0.76.0

Compare Source

🚀 Enhancements

feat: adds support for track_latest @​gberenice (#​246)

what

• Adds track_latest and bumps provider version to v5.37.0 accordingly.

why

• Allow users to make the task definitions track always the latest one if track_latest is set to true.

references

• Closes https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/issues/221
• See original addition of this argument to the provider here: https://github.com/hashicorp/terraform-provider-aws/pull/30154

🤖 Automatic Updates

Update .github/settings.yml @​osterman (#​245)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @​osterman (#​244)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update release workflow to allow pull-requests: write @​osterman (#​241)

what

• Update workflow (.github/workflows/release.yaml) to have permission to comment on PR

why

• So we can support commenting on PRs with a link to the release

Update GitHub Workflows to use shared workflows from '.github' repo @​osterman (#​240)

what

• Update workflows (.github/workflows) to use shared workflows from .github repo

why

• Reduce nested levels of reusable workflows

v0.75.0

[Compare Source](https://redirect.gith...

v1.535.0

Migrate component from cloudposse/terraform-aws-components

v1.534.0

Migrate component from cloudposse/terraform-aws-components

v1.533.0

Migrate component from cloudposse/terraform-aws-components

v1.532.0

Migrate component from cloudposse/terraform-aws-components