Site Name check does not seem to actually check for availability #69
Assignees
Comments
|
Strange, it works for me: Maybe something is throwing off the check in your case. Try F12 to watch requests. |
|
Will check again and get back to you. |
|
It appears that if there is a default value (say, "contosoapp") it does not get checked. It would appear to to the equivalent of OnChanged() for when the box itself gets changed via user input. |
|
Oh I see. Yes, that's likely the bug! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I deploy multiple times with the same site name, I expected the slingshot page to check for global uniqueness within Azure for the site name (based on "Name Is Available" language) and fail the check; however, it can pass the check but fail in deployment because of a name collision (which leads me to believe my understanding is incorrect). If Site name is checking for something else (but implying availability), this needs to be communicated. If it is supposed to avoid this collision, it is not doing so with complete accuracy.
Also: please document those parameters with special treatment (collision checking, etc. ).
The text was updated successfully, but these errors were encountered: