Document per-cloud resource tag validation rules#4718
Merged
Conversation
- Replace old GCP-only character rules with per-cloud table - Add per-cloud rules section with AWS, Azure, GCP limits - Raise max tags from 20 to 50 - Note template variable exclusion from character checks - Note that resolved values are always lowercased
bratseth
approved these changes
May 20, 2026
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
2 participants
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.
Update the
resource-tagssection ofdeployment.xmlreference to document per-cloud validation rules for enclave resource tags.Changes:
[a-z0-9_-], max 63 chars) with per-cloud rules table covering AWS, Azure, and GCPRelated: vespa-engine/vespa#36953
FYI: @bratseth, @thomasht86