[AppService] az webapp up/create: better error handling of app name with period#16623
Merged
[AppService] az webapp up/create: better error handling of app name with period#16623
Conversation
Member
|
@calvinsID You updated your profile picture. 😎 |
qwordy
approved these changes
Jan 22, 2021
Contributor
Author
|
haha yeah @qwordy it was about time i updated |
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
3 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.
Description
Fixes #16622
Run
az webapp up/createwith a name that has a period (".")Made this fix on CLI instead of the checkNameAvailability API because "." is valid for a full site hostname (URL's allow periods), just not valid for an appservice name.
I think portal also does some frontend validations like this when creating a webapp (though I haven't confirmed this)
Testing Guide
Expected msg:
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.