Can you please provide a reason for this change?

It seems that azure go SDK lift the restriction of container name.
Therefore, we could name azure container more flexible

The old restriction of container name is that the length must be 32.

@plutoshe Can you link the related change in the commit message or comment on github?

I found this problem by accessing azure storage yesterday.
Maybe it's my old logic error. I wrongly think the container name length restriction.

It seems that azure go SDK lift the restriction of container name.

Your change is based on an uncertain assumption. If you can provide more information, the reviewer can have a better context of the change.

For example, you might share me which commit in azure go sdk changes the restriction (https://github.com/Azure/azure-sdk-for-go). Or how do you know the restriction changed.

Maybe it's my old logic error. I wrongly think the container name length restriction.

We want to make sure this time we can get it right. So we want to be more careful. It would be helpful if you can find any related doc in go sdk.

Sure.
I don't remember why I set the this restriction before. It seems odd.
Anyway, I will find related docs.
Thanks for comments.

@plutoshe Sure. Thanks!

Azure Naming Rules
When I find this docs, I find that my old code and logic is wrong here,
@xiang90 , Thanks for checking, I will check my logic and code more rigorous when I submit.
I will reimplement the name checking mechanism here.

Container Names
A container name must be a valid DNS name, conforming to the following naming rules:
Container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character.

Every dash (-) character must be immediately preceded and followed by a letter or number; consecutive dashes are not permitted in container names.

All letters in a container name must be lowercase.

Container names must be from 3 through 63 characters long.

We can start with the simplest ones: length. I am OK with adding a few TODOs.

Sure, I will list some TODOs, and do the length inspection first.

@plutoshe Great. Thanks for finding the doc and putting the effort.

why this break the test?