renovate[bot]
commented
7 months ago Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (0.50.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
This PR contains the following updates:
0.41.0->0.50.0Release Notes
cloudposse/terraform-aws-ec2-instance (cloudposse/ec2-instance/aws)
### [`v0.50.0`](https://togithub.com/cloudposse/terraform-aws-ec2-instance/releases/tag/0.50.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-ec2-instance/compare/0.49.0...0.50.0) - AWS provider V4 Compatibility ### [`v0.49.0`](https://togithub.com/cloudposse/terraform-aws-ec2-instance/releases/tag/0.49.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-ec2-instance/compare/0.48.0...0.49.0)Adding external ENIs @jamengual (#159)
#### what Add the ability to add external ENIs to the instance #### why For ec2 instances deployments clusters where the IPs are required to be unique and not change it is necessary to create ENIs outside of this module so that the instance termination does not change the ENI and IP attached. #### referencesSync github @max-lobur (#156)
Rebuild github dir from the templateOnly get data.aws_ami.info if it's actually required @y3ti (#151)
#### what - Use data.aws_ami.info only if it's actually required #### why - Fix Your query returned no results" error once the AMI ID is not listed within AWS marketplace #### references - closes [#150](https://togithub.com/cloudposse/terraform-aws-ec2-instance/issues/150) - closes [#143](https://togithub.com/cloudposse/terraform-aws-ec2-instance/issues/143)Do not set iops and throughput for non-supporting volume types @cinacio (#142)
#### what * Only set iops and throughput arguments for volume types supporting those options. #### why * According to the documentation for the [aws_ebs_volume resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ebs_volume), the `iops` argument is only valid for volumes types `io1`, `io2` & `gp3`. * According to the same documentation, the `throughput` argument is only valid for volume type `gp3`. * Setting the throughput of a `gp2` volume to "0" triggers the following error > Error: expected throughput to be in the range (125 - 1000), got 0 > > with module.instance.aws_ebs_volume.default\[0], > on .terraform/modules/instance/main.tf line 178, in resource "aws_ebs_volume" "default": > 178: throughput = local.ebs_throughput #### references - closes [#137](https://togithub.com/cloudposse/terraform-aws-ec2-instance/issues/137)Adding support for secondary private ips @vale21 (#153)
#### what * Adding support for secondary private ips to EC2 instances created with this module #### why * I cannot set secondary private IPs to my EC2 instance using your module #### references * Fixes #152Support AWS partition for SSM resources @dlundgren (#148)
#### what * SSM patch is currently hardcoded to `aws` so this doesn't work when trying to use the role with AWS GovCloud. #### why * This allows the role to work in with AWS GovCloud #### references * The cloudwatch-alarm supports the AWS GovCloud partitionTurn tenancy validation message into English prose @irl (#144)
Adds a period at the end of the error message. #### what A single character change to make this into English prose. #### why ā· ā Error: Invalid validation error message ā ā on .terraform/modules/instance/variables.tf line 378, in variable "tenancy": ā 378: error_message = "Tenancy field can only be one of default, dedicated, host" ā ā The validation error message must be at least one full sentence starting with an uppercase letter and ending with a period or question mark. ā ā Your given message will be included as part of a larger Terraform error message, written as English prose. For broadly-shared modules we suggest using a similar writing style so that the overall result will be consistent. āµAdd ability to configure instance tenancy @RothAndrew (#141)
#### what * Add new variable `tenancy` that allows user to configure instance tenancy (`default` (default), `dedicated`, or `host`) #### why * An organization that I work with has a security policy that requires use of dedicated tenancy. This PR adds the capability to do that when using this module. #### references * https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance#tenancy * Closes #139Added support for gp3 and io2 both root and ebs volumes (fixed copy of #117) @tbpoetke (#136)
#### what - Added support for io2 and gp3 volumes #### why - original PR had conflicts, this will work hopefully - io2 and gp3 are new more performant volumes therefore they should be supported #### references - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance#ebs-ephemeral-and-root-block-devices - Closes [https://github.com/cloudposse/terraform-aws-ec2-instance/issues/114](https://togithub.com/cloudposse/terraform-aws-ec2-instance/issues/114)git.io->cloudposse.tools update @dylanbannon (#126)
#### what and why Change all references to `git.io/build-harness` into `cloudposse.tools/build-harness`, since `git.io` redirects will stop working on April 29th, 2022. #### References - DEV-143support-kms-key-id-for-root-volume @woz5999 (#128)
#### what * Support customer managed kms key for block device #### why * This is supported for other EBS volumes in the module * CMK should be supported for root device as wellAdding in support for ec2 metadata_tags @wschultz (#122)
#### what * This adds in an option to turn on the metadata_tags (or off, the default) inside the aws_instance metadata_options. #### why * There are options for http_endpoint, http_put_response_hop_limit and http_tokens already but not for metadata_tags. This adds that functionality.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 is behind base branch, or you tick the rebase/retry checkbox.
š Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.