Skip to content

Releases: cloudposse-terraform-components/aws-ec2-instance

v1.536.0

03 Jun 15:41
6f3a9d6
Compare
Choose a tag to compare

🤖 Automatic Updates

Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#34) ## 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/ec2-instance/aws to v2 @[renovate[bot]](https://github.com/apps/renovate) (#32) This PR contains the following updates:
Package Type Update Change
cloudposse/ec2-instance/aws (source) module major 1.4.0 -> 2.0.0

Release Notes

cloudposse/terraform-aws-ec2-instance (cloudposse/ec2-instance/aws)

v2.0.0

Compare Source

Update Ubuntu AMI query @​goruha (#​215)

what

  • Update Ubuntu AMI to 22.04
  • Fix enabled flag

why

  • AMI 18.04 is deprecated
  • Not all resources used to support the enabled flag

🤖 Automatic Updates

Replace Makefile with atmos.yaml @​osterman (#​214)

what

  • Remove Makefile
  • Add atmos.yaml

why

  • Replace build-harness with atmos for readme genration

References

  • DEV-3229 Migrate from build-harness to atmos

v1.6.1

Compare Source

fix: allow stopping instance before detachment and/or forced ebs detachments @​Hamza-Olol (#​212) Added support to the EBS volume attachment resource for the `force_detach` and `stop_instance_before_detaching` arguments.

These changes allow users to:
- Force the detachment of EBS volumes.
- Stop instances before detaching volumes, ensuring smooth resource teardown during Terraform destroy operations.

why

I cannot delete my Terraform resources using a standard Terraform destroy because I have attached additional ebs volumes to my instance and then ran disk configuration changes in my instance, for example, combined multiple ebs volumes into a striped disk config.

Business use cases may require additional EBS volumes, along with specific disk configurations for the volumes attached to EC2 instances.

When attempting to delete resources via Terraform, the destroy process fails due to issues with EBS volume attachments. These issues include timeouts or the inability to delete volumes because they are in a "busy" state.

The problem arises because Terraform attempts to detach EBS volumes before deleting/stopping the EC2 instance, leading to failures if the volume cannot be detached.

To address this, Terraform introduced the force_detach and stop_instance_before_detaching arguments, which allows forced detachment and/or stopping of the instance prior to detaching volumes. These enhancements mitigate the destroy-time failures and ensure smoother resource cleanup.

references

The force_detach and stop_instance_before_detaching arguments were introduced in Terraform AWS provider version v3.62.0.

Additional details and discussion about this issue can be found in this GitHub thread.

🤖 Automatic Updates

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

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 (#​207)

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 (#​206)

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

v1.6.0

Compare Source

fix: remove lifecycle ignore changes for ami argument @​nitrocode (#​205)

what

  • remove lifecycle ignore changes for ami argument

why

  • This change looks unintentional based on the PR description
  • We'd like to allow AMIs to recreate the EC2 for singletons that aren't production facing

references

v1.5.0

Compare Source

feat: Add missed tags @​MaxymVlasov (#​204)

what

Add tags to resources where they missed

🤖 Automatic Updates

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

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 (#​199)

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 (#​198)

what

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

why

  • Reduce nested levels of reusable workflows

v1.4.1

Compare Source

feat: disable_api_stop option @​flightlesstux (#​197)

what

Control your EC2 Disable API with your Terraform

why

Because, AWS SDK and cli are supporting.

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance#disable_api_stop

🤖 Automatic Updates

Update GitHub Workflows to Fix ReviewDog TFLint Action @​osterman (#​196)

what

  • Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action

why

  • The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @​osterman (#​195)

what

  • Update workflows (.github/workflows/settings.yaml)

why

  • Support new readme generation workflow.
  • Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​192)

what

  • Install latest GitHub Action Workflows

why

  • Use shared workflows from cldouposse/.github repository
  • Simplify management of workflows from centralized hub of configuration

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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.


  • <!-- rebase-chec...
Read more

v1.535.2

01 Apr 10:07
2fa678a
Compare
Choose a tag to compare

🤖 Automatic Updates

chore(deps): update tflint plugin terraform-linters/tflint-ruleset-aws to v0.38.0 @[renovate[bot]](https://github.com/apps/renovate) (#6) This PR contains the following updates:
Package Type Update Change
terraform-linters/tflint-ruleset-aws plugin minor 0.23.1 -> 0.38.0

Release Notes

terraform-linters/tflint-ruleset-aws (terraform-linters/tflint-ruleset-aws)

v0.38.0

Compare Source

What's Changed

Breaking Changes
  • Update AWS provider/module and generated content by @​wata727 in https://github.com/terraform-linters/tflint-ruleset-aws/pull/837
    • Remove Amazon Chime rules
      • aws_chime_voice_connector_group_invalid_name
      • aws_chime_voice_connector_invalid_aws_region
      • aws_chime_voice_connector_invalid_name
      • aws_chime_voice_connector_logging_invalid_voice_connector_id
      • aws_chime_voice_connector_origination_invalid_voice_connector_id
      • aws_chime_voice_connector_streaming_invalid_voice_connector_id
      • aws_chime_voice_connector_termination_credentials_invalid_voice_connector_id
      • aws_chime_voice_connector_termination_invalid_default_phone_number
      • aws_chime_voice_connector_termination_invalid_voice_connector_id
Enhancements
Chores

Full Changelog: terraform-linters/tflint-ruleset-aws@v0.37.0...v0.38.0

v0.37.0

Compare Source

Breaking Changes
  • #​789 #​798: Update AWS provider/module and generated content
    • Removed the following rules
      • aws_service_discovery_http_namespace_invalid_name
      • aws_service_discovery_private_dns_namespace_invalid_name
      • aws_service_discovery_public_dns_namespace_invalid_name
Enhancements
Read more

v1.535.1

01 Apr 08:29
b5eaad2
Compare
Choose a tag to compare
chore: add tests @RoseSecurity (#17) ## what
  • Add basic component test
  • Add disabled component test
  • Test component drifting

why

  • Test basic component features
  • Verify that the component does not create any resources when input enabled: false set
  • Verify that the component does not drift on a second run with the same inputs

references

Summary by CodeRabbit

  • Chores
    • Updated an infrastructure module to a newer version.
    • Removed an obsolete test script.
  • New Features
    • Introduced several new YAML configuration files that enhance CLI settings and infrastructure component setups, including network, compute, account mapping, and vendor configurations.
  • Tests
    • Added a comprehensive test suite to validate EC2 instance components, ensuring proper deployment and stability.

🤖 Automatic Updates

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

v1.535.0

04 Jan 11:20
df4e52c
Compare
Choose a tag to compare

Migrate component from cloudposse/terraform-aws-components

v1.534.0

04 Jan 11:04
df4e52c
Compare
Choose a tag to compare

Migrate component from cloudposse/terraform-aws-components

v1.533.0

13 Dec 19:50
d01d093
Compare
Choose a tag to compare

Migrate component from cloudposse/terraform-aws-components

v1.532.0

27 Nov 11:26
8e8f451
Compare
Choose a tag to compare

Migrate component from cloudposse/terraform-aws-components