[CONTP-669] Document availability_zone tag deprecation for ECS Fargate#22502
Draft
[CONTP-669] Document availability_zone tag deprecation for ECS Fargate#22502
Conversation
Add the deprecated availability_zone tag to the out-of-the-box tags documentation and clarify that it is deprecated in favor of availability-zone. Both tags are currently sent by the Agent but availability_zone may be removed in a future release. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add the deprecated availability_zone tag to the out-of-the-box tags documentation and clarify that it is deprecated in favor of availability-zone. Both tags are currently sent by the Agent but availability_zone may be removed in a future release.
What does this PR do?
Motivation
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged