feat: Adding availability_zone
to the outputs of the module
#265
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.
Description
The
availability_zone
of the instance is very useful information to use outside of the module. This PR provides that information.Motivation and Context
When creating an external or auxiliary
aws_ebs_volume
for the EC2 instance, it requires an availability zone argument. Often times, we would like to have the EBS volume in the same AZ as the EC2. Having that information would make that design much easier.Resolves #264
Breaking Changes
None
How Has This Been Tested?
examples/*
projectsIn terraform, I declared a ec2 module with my revisions and used the outputs for aws_volume_attachment and aws_ebs_volume arguements:
Environment: