Releases: cloudposse/terraform-aws-ec2-bastion-server
v0.28.0
v0.27.0
aws_iam_instance_profile tags pass through @heathsnow (#79)
what
- Pass through tags to the
aws_iam_instance_profile
resource
why
- There's often validation regarding tagging resources. In my case I need specific key/values to exist on all resources that support tags.
references
- Closes #78
v0.26.3
🤖 Automatic Updates
chore(deps): update terraform cloudposse/security-group/aws to v0.3.1 @renovate (#74)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/security-group/aws (source) | module | minor | 0.2.0 -> 0.3.1 |
Release Notes
cloudposse/terraform-aws-security-group
v0.3.1
🐛 Bug Fixes
Restore Terraform 0.13 support, fix #12 @Nuru (#15)
#### what - Restore Terraform 0.13 support - Fix #12 - Add additional tests #### why - Lots of people still using Terraform 0.13 - Useful, requested functionality - Ensure against reversion of #12 or #13, protect against future issues with null valuesv0.3.0
refactor: rework value mapping for for_each and update dependencies @SweetOps (#11)
#### what * rework value mapping for `for_each` * bump minimal required version of TF to `0.14.0` * bump terratest to `v0.32.8` #### why * terraform has weird limitation which blocks using of dynamic values inside the `for_each` loop ```sh The "for_each" 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 for_each depends on. ```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, check this box.
This PR has been generated by WhiteSource Renovate. View repository job log here.
v0.26.2
v0.26.1
🤖 Automatic Updates
chore(deps): update terraform cloudposse/security-group/aws to v0.2.0 @renovate (#73)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/security-group/aws (source) | module | minor | 0.1.4 -> 0.2.0 |
Release Notes
cloudposse/terraform-aws-security-group
v0.2.0
self conflicts with cidr_blocks error fix @maximmi (#14)
#### what * default value for `self` field of security group rule changed to `null` #### why * With the provider `hashicorp/aws` `v3.38.0` new restrictions have been added to `aws_security_group_rule` resource #### references * closes #13 * https://github.com/hashicorp/terraform-provider-aws/issues/15606 * https://github.com/hashicorp/terraform-provider-aws/pull/18467Configuration
📅 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, check this box.
This PR has been generated by WhiteSource Renovate. View repository job log here.
v0.26.0
v0.25.0
v0.24.0
- No changes
v0.23.0
v0.22.0
Amazon linux v2 updates. SSM and Security Group Module @htplbc (#64)
what
- Use latest-ami based on owner and filters
- Use
cloudposse/terraform-aws-security-group
module - Deprecate Ubuntu AMI logic and user-data scripts.
- Flag to Enable SSM Agent
- EBS Attached storage
why
- SSM Agent functionality relies on IAM, not antiquated SSH keys
- Requires no direct connectivity
- Instances can reside in private subnet
- Latest AMI logic for Security
- Standardize on using security group module