provider/aws: Fix AMI creation from snapshot issue #11842
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously the AMI creation accepted a static value for the AMI's block device's volume size.
This change allows the user to omit the
volume_size
attribute, in order to mimic the AWS API behavior, which will use the EBS Volume's size.Also fixes a potential panic case when setting
iops
on the AMI's block device.The
aws_ami
resource previously didn't have any acceptance tests, adds two acceptance tests and a full testing suite for theaws_ami
resource, so further tests can be written, as well as expansion upon the otheraws_ami_*
acceptance testsFixes: #11655