You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This one is a bit tricky. Let's say I name my project test. Eventually when I create a resource group it will include the project name, the DC name, the deployment type and for dev deployments even an ID for the dev. But if someone else happens to pick the same project name then we will have a collision.
The situation is even uglier (although statistically less likely) for individual resources where our cons up names might theoretically collide with someone else's name.
Right now we would just return a blind error and hope the user can figure it out. But ideally we would detect this kind of situation, ideally during the init process, and warn the user.
The text was updated successfully, but these errors were encountered:
This one is a bit tricky. Let's say I name my project test. Eventually when I create a resource group it will include the project name, the DC name, the deployment type and for dev deployments even an ID for the dev. But if someone else happens to pick the same project name then we will have a collision.
The situation is even uglier (although statistically less likely) for individual resources where our cons up names might theoretically collide with someone else's name.
Right now we would just return a blind error and hope the user can figure it out. But ideally we would detect this kind of situation, ideally during the init process, and warn the user.
The text was updated successfully, but these errors were encountered: