Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs/resource/aws_autoscaling_group: Clarify usage of availability_zones #3897

Merged
merged 1 commit into from
Mar 23, 2018

Conversation

bflad
Copy link
Member

@bflad bflad commented Mar 23, 2018

Also updates the examples to use vpc_zone_identifier instead of availability_zones as VPC usage should be more common than EC2-Classic usage.

Followup documentation update for #1190
Closes #3863
Closes #3449
Closes #3440
Closes #3439
Closes #3186
Closes #2953
Closes #2880
Closes #2797
Closes #2435
Closes #2252
Closes #1990
Closes #1931
Closes #1784
Closes #1630
Closes #1527
Closes #1376

Also updates the examples to use vpc_zone_identifier instead of availability_zones as VPC usage should be more common than EC2-Classic usage.
@ghost ghost added size/XS Managed by automation to categorize the size of a PR. documentation Introduces or discusses updates to documentation. labels Mar 23, 2018
@bflad bflad added the service/autoscaling Issues and PRs that pertain to the autoscaling service. label Mar 23, 2018
@bflad bflad added this to the v1.12.0 milestone Mar 23, 2018
@bflad bflad requested a review from a team March 23, 2018 13:53
@bflad bflad merged commit 301c19c into master Mar 23, 2018
@bflad bflad deleted the d-aws_autoscaling_group-az-vpc-diffs branch March 23, 2018 14:14
@ghost
Copy link

ghost commented Apr 7, 2020

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!

@ghost ghost locked and limited conversation to collaborators Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.