Releases: cloudposse-terraform-components/aws-bastion
Releases · cloudposse-terraform-components/aws-bastion
v1.536.1
🤖 Automatic Updates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#25)
## what This is an auto-generated PR that updates the README.md and docswhy
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) (#4)
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
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
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-roleto
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)
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
🚀 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
spacelifttest suite is broken, and we never previously required it to work, so it is now skipped
- The
- Update test suite to use
gov1.21 and update dependencies
why
🤖 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-securityin hashicorp/go-getter#497New Contributors
@dduzgun-securitymade their first contribution in hashicorp/go-getter#497Full 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
gitcommands hashicorp/go-getter#483- Fixed a bug in
.netrchandling if the file does not exist hashicorp/go-getter#433Full 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-tsccrin hashicorp/go-getter#432- SEC-090: Automated trusted workflow pinning (2023-09-11) by
@hashicorp-tsccrin hashicorp/go-getter#454- SEC-090: Automated trusted workflow pinning (2023-09-18) by
@hashicorp-tsccrin hashicorp/go-getter#458- don't change GIT_SSH_COMMAND when there is no sshKeyFile by
@jbardinin hashicorp/go-getter#459New Contributors
@hashicorp-tsccrmade their first contribution in
Contributors
goruha
Assets 2
v1.536.0
fix: adjust functions to allow for a clean deletion @RoseSecurity (#17)
## what- When the following command is ran on the component, the deletion fails:
# Destroy resources
atmos terraform destroy bastion -s <stack>Error:
╷
│ Error: Invalid index
│
│ on main.tf line 132, in module "bastion_autoscale_group":
│ 132: user_data_base64 = join("", data.cloudinit_config.config[0][*].rendered)
│ ├────────────────
│ │ data.cloudinit_config.config is empty tuple
│
│ The given key does not identify an element in this collection value: the collection has no elements.
╵
Releasing state lock. This may take a few moments...why
data.cloudinit_config.configis a list with count = 0 or 1- We're accessing the first (and only) element when it exists
- We want a safe fallback when it’s disabled
- Clean up outputs when disabled
Summary by CodeRabbit
- Bug Fixes
- Improved error handling during initialization to gracefully handle missing configuration details.
- Updated output derivation for profile information, ensuring more consistent and reliable data presentation.
Contributors
RoseSecurity
