Repository navigation
Conversation
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
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.
Change Summary
When a Tigris bucket name is invalid, the creation API returns "The specified bucket is not valid." This change checks the selected name before creation and explains which naming rule failed, with a link to the Tigris documentation.
Validation runs after name selection, so it covers the --name flag, names derived from app names, and launch overrides. Blank names still request an automatically generated name.
The tests cover 28 cases, including invalid names, valid length boundaries, override precedence, generated names, and names used by other providers.
Checks passed:
Fixes #4728.
Documentation