Skip to content

Remove non-inclusive terminology from aws_availability_zones data source attribute names #13766

@breathingdust

Description

@breathingdust

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Use the next major release as an opportunity to remove non-inclusive terminology in the provider codebase, documentation, and examples. We will be removing words whose meanings, origin, or associations are contrary to our Principles.

New or Affected Resource(s)

  • aws_availability_zones

Potential Terraform Configuration

Before:

data "aws_availability_zones" "test" {
  blacklisted_zone_ids = []
  blacklisted_names = []
}

After:

data "aws_availability_zones" "test" {
  skip_zone_ids = []
  skip_names = []
}

References

Metadata

Metadata

Assignees

Labels

breaking-changeIntroduces a breaking change in current functionality; usually deferred to the next major release.enhancementRequests to existing resources that expand the functionality or scope.service/ec2Issues and PRs that pertain to the ec2 service.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions