Today we have multiple ways to define settings when a user needs to create a repository:
- in
elasticsearch.yml file using repositories.xxx prefix where xxx is the implementation name like s3, hdfs...
- when creating the repository itself with
PUT _snaphot/repo
Based on discussion we have on #22762 and on #22301 and also internally, I think we should reduce the overall complexity and completely remove support for global settings like this.
Actually, the creation of a repository is most of the time a unique manual operation so providing settings at repository creation time does not bring a lot of complexity for the end user.
And that will simplify a lot our code and our tests.
The plan would be:
- Deprecate
repositories.xxx settings in 5.x:
- Remove
repositories.xxx settings in 6.x (master branch):
Today we have multiple ways to define settings when a user needs to create a repository:
elasticsearch.ymlfile usingrepositories.xxxprefix wherexxxis the implementation name likes3,hdfs...PUT _snaphot/repoBased on discussion we have on #22762 and on #22301 and also internally, I think we should reduce the overall complexity and completely remove support for global settings like this.
Actually, the creation of a repository is most of the time a unique manual operation so providing settings at repository creation time does not bring a lot of complexity for the end user.
And that will simplify a lot our code and our tests.
The plan would be:
repositories.xxxsettings in 5.x:repositories.azuresettings #22856)repositories.xxxsettings in 6.x (master branch):repositories.azuresettings #23262)