-
Notifications
You must be signed in to change notification settings - Fork 14
_
is a forbidden character for container (repository)
#21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@dadoonet the documentation fix is good, but I think we should either move snapshot name validation from SnapshotService to the repository level and make it possible to override snapshot validation rules by repository implementation or we can try to escape the snapshot name when creating the snapshot. I would prefer the former solution even though it is more involving. |
@imotov agreed. Having a new method which actually let every repository plugin validate the repository settings would be nice for the future. Something like:
At the moment, I suggest that I first update the documentation. Wondering when this new feature should come? Within elasticsearch 2.0? Having that in 1.4 will break the plugin compatibility (not a big deal though as I update plugins for every elasticsearch major release). |
_
is a forbidden character for snapshots_
is a forbidden character for container (repository)
According to [Containers naming guide](http://msdn.microsoft.com/en-us/library/dd135715.aspx): > 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 need to fix the documentation and control that before calling Azure API. The validation will come with issue #27. Closes #21.
According to Containers naming guide:
We need to fix the documentation and control that before calling Azure API.
The text was updated successfully, but these errors were encountered: