Releases: cloudposse/terraform-aws-ec2-bastion-server
v0.31.1
fix: ec2 instance constant termination/creation if ebs enabled @www44 (#239)
## whatFix AWS instance idempotency if an EBS volume is configured.
why
- To prevent AWS ec2 instance termination by each terraform run, even if no changes exist.
references
🤖 Automatic Updates
Migrate new test account @osterman (#240)
## what - Update `.github/settings.yml` - Update `.github/chatops.yml` fileswhy
- Re-apply
.github/settings.yml
from org level to getterratest
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 (#238)
## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` fileswhy
- 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 (#237)
## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` fileswhy
- 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.31.0
Important
Earlier versions (everything since v0.27.0) were marked pre-release because this module uses the obsolete version of terraform-aws-security-group (pre v0.4.0) and there are breaking changes in 0.4.0, and further breaking changes in v2.0.0, and we wanted to encourage people to wait until we had an updated version using terraform-aws-security-group
v2, to limit the impact of migration.
At this point, it's obviously too long a wait, and despite the earlier versions being marked as pre-release, they were released to the Terraform registry and people are using them, so we are not marking these versions as pre-release anymore. However, if anyone has any issues with the security group created by this module, we invite you to upgrade it to use the much more capable and up-to-date terraform-aws-security-group
v2. See #234
What's Changed
Full Changelog: 0.30.1...0.31.0
v0.30.1
git.io->cloudposse.tools update, Lock down CODEOWNERS @dylanbannon (#96)
what and why
- Change all references to
git.io/build-harness
intocloudposse.tools/build-harness
, sincegit.io
redirects will stop working on April 29th, 2022. - Lock down this repo via CODEOWNERS until breaking changes from v0.28.0 are reverted, to avoid publishing new releases that perpetuate the breaking changes.
References
- DEV-143
v0.30.0
v0.29.0
Override the `ami` @nitrocode (#81)
what
- Override the
ami
why
- Sometimes you want to ensure that your plan is the same and it's difficult to do if the ami is different. By allowing the module to override the ami, I can pin it down and only show the plan relevant to my other changes.
references
N/A
v0.28.5
🚀 Enhancements
Fix: Run `make github/init`, Allow for `context.tf` That Has `null-label:0.25.0` @korenyoni (#94)
what
- Run
make github/init
. - Bump
security-group
module to minimum version withcontext.tf
that hasnull-label:0.25.0
. - Bump
route53-cluster-hostname
module to latest.
why
- Running
make github/init
updates GHA-related files, including those relating torelease-drafter
which will now allow ano-release
label that can be used to consolidate multiple PRs into a single release. - Allow for a
context.tf
that hasnull-label:0.25.0
to be used with this module, without having to introduce changes allowing for https://github.com/cloudposse/terraform-aws-security-group0.4.0+
(out of scope for this PR).
references
🐛 Bug Fixes
Fix: Run `make github/init`, Allow for `context.tf` That Has `null-label:0.25.0` @korenyoni (#94)
what
- Run
make github/init
. - Bump
security-group
module to minimum version withcontext.tf
that hasnull-label:0.25.0
. - Bump
route53-cluster-hostname
module to latest.
why
- Running
make github/init
updates GHA-related files, including those relating torelease-drafter
which will now allow ano-release
label that can be used to consolidate multiple PRs into a single release. - Allow for a
context.tf
that hasnull-label:0.25.0
to be used with this module, without having to introduce changes allowing for https://github.com/cloudposse/terraform-aws-security-group0.4.0+
(out of scope for this PR).
references
v0.28.4
🚀 Enhancements
Update context.tf @cloudpossebot (#93)
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.
🤖 Automatic Updates
Update context.tf @cloudpossebot (#93)
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.
v0.28.3
🚀 Enhancements
Fix: var.zone_id conditional logic @korenyoni (#83)
what
- Fix checks on
var.zone_id
in order to handlevar.zone_id
being null.
why
var.zone_id
is only expected to be an empty string, but the module does not handle it beingnull
.
references
- N/A
🐛 Bug Fixes
Fix: var.zone_id conditional logic @korenyoni (#83)
what
- Fix checks on
var.zone_id
in order to handlevar.zone_id
being null.
why
var.zone_id
is only expected to be an empty string, but the module does not handle it beingnull
.
references
- N/A
v0.28.2
🚀 Enhancements
Use instance profile if created @nitrocode (#82)
what
- Use instance profile if created
why
- It creates the instance profile but does not associate it with the ec2 instance
references
N/A
🐛 Bug Fixes
Use instance profile if created @nitrocode (#82)
what
- Use instance profile if created
why
- It creates the instance profile but does not associate it with the ec2 instance
references
N/A
v0.28.1
🐛 Bug Fixes
Fix conditional logic for creating IAM role @korenyoni (#80)
what
- Fix conditional logic for creating IAM role
- Bump modules in
examples/complete
.
why
- IAM Role was being created even when
var.enabled=false
references
- Issue identified in cloudposse/terraform-aws-components#340