Fix storage account name availability check to provide meaningful error messages #58
+129
−27
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.
The storage account name validation in interactive mode was failing with incomplete error messages when Azure CLI errors occurred. Users would see truncated messages like:
Instead of helpful information about why the validation failed.
Root Cause
The issue had two parts:
2>$nullredirection meant authentication errors and other CLI failures were hidden, causingConvertFrom-Jsonto receive no input and return null-notmatchoperator is case-insensitive, so format validation wasn't catching uppercase letters properlyChanges Made
2>&1and check$LASTEXITCODEto detect CLI failures"Storage account name must be 3-24 lowercase alphanumeric characters.""Storage account name 'name' could not be validated. Azure CLI error: Please run 'az login' to setup account.""Storage account name 'name' is not available: The storage account named name is already taken."-cnotmatchfor case-sensitive format validationTest-StorageAccountName.ps1fileTesting
The fix now handles all failure scenarios gracefully:
Fixes #57.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
http://168.63.129.16:80/machine//usr/bin/python3 -u bin/WALinuxAgent-2.13.1.1-py3.9.egg -collect-logs(http block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.