WindowsAzure/azure-sdk-tools — Issue #73: Publish-AzureService fails to create a service with contoso-tasklist name
Author: yavorg
Created: 2012-01-05 00:17:34+00:00
State: open

kirillg says: Our logic to infer a valid default storage account from a service name is not robust enough. contoso-tasklist is a valid service name, but an invalid storage account name. Publish-AzureService just returns 400.

We should either
1) error "No storage account name is specified, attempting to create contoso-tasklist... contoso-tasklist is not a valid storage account name, please specify a valid storage account name that either exists or that you want us to create"

2) or provide a robust function that infers a valid storage account name from a service name (for the case when storage account is not specified).

Not for this release, but something worth fixing.

For example we could automatically remove special characters like "-" or replace them with something acceptable.

jcookems says: Changing names can cause unintended consequences. I'd suggest that (1) is a better path, alongh with a link/description of the naming rules. (I think they are lowercase ASCII a-z, 0-9, and a few other special characters)

** Kirill has already checked in a small fix that JUST addresses "-". We still need a more comprehensive fix to address other special characters. **