Originally reported by @JeyDotC
Please, check that container name is all lowercase in AzureDataBusGuard or lower case the container name before creating it, not doing so caused me to struggle for hours with a not very describing 'bad request' error.
I didn't remember that restriction on container names(my bad) but I think I shouldn't if NServiceBus is intended to reduce the amount of details I must remember to configure the DataBus feature.
If you think one just have to be careful on how to name containers, which I think is completely valid, I'd appreciate that you state that in your documentation.
Who's affected
AzureBlobStorageDataBus
and specifies invalid characters for container nameSymptoms
Attention Fixed in NServiceBus.AzureBlobStorageDataBus repo, but since that one is not releasable, needs to be fixed in NServiceBus.Azure and released.
Originally reported by @JeyDotC Please, check that container name is all lowercase in AzureDataBusGuard or lower case the container name before creating it, not doing so caused me to struggle for hours with a not very describing 'bad request' error.
I didn't remember that restriction on container names(my bad) but I think I shouldn't if NServiceBus is intended to reduce the amount of details I must remember to configure the DataBus feature.
If you think one just have to be careful on how to name containers, which I think is completely valid, I'd appreciate that you state that in your documentation.
Regards.