Support ena_support

[nbrownus]

Partially Fixes #206

Changes proposed in this pull request:

• Exposes ena_support on aws_ami

[bflad]

LGTM -- just needs the documentation which I'll add in a commit after yours. 🚀

2 tests passed (all tests)
=== RUN   TestAccAWSAMI_basic
--- PASS: TestAccAWSAMI_basic (59.25s)
=== RUN   TestAccAWSAMI_snapshotSize
--- PASS: TestAccAWSAMI_snapshotSize (59.52s)

[bflad]

FYI this new argument needs to be documented in website/docs/r/ami.html.markdown as well.

[bflad]

This has been released in version 1.30.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[rkhozinov]

Hey, @bflad @nbrownus what about the related change for the aws_ami_copy resource?

aws_ami_copy.encrypted_ami (new resource required)
      id:                                                 "ami-***" => <computed> (forces new resource)
      architecture:                                       "x86_64" => <computed>
      description:                                        "AMI***" => "AMI***"
      ebs_block_device.#:                                 "9" => <computed>
      ena_support:                                        "true" => "false" (forces new resource)
      encrypted:                                          "true" => "true"
      ephemeral_block_device.#:                           "0" => <computed>

[samjgalbraith]

I think this is causing Terraform to want to replace our AMIs. It states that the state of the current AMI resource has a value ena_enabled = true (even though the flag was never available via Terraform before, it seems to have had true by default) and it wants to replace the AMI to change ena_enabled to false.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!