Skip to content
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

System indices should be able to bypass restricted index auto creation #61642

Closed
Tracked by #50251
jaymode opened this issue Aug 27, 2020 · 1 comment · Fixed by #62984
Closed
Tracked by #50251

System indices should be able to bypass restricted index auto creation #61642

jaymode opened this issue Aug 27, 2020 · 1 comment · Fixed by #62984
Assignees
Labels
:Core/Infra/Core Core issues without another label >enhancement Team:Core/Infra Meta label for core/infra team

Comments

@jaymode
Copy link
Member

jaymode commented Aug 27, 2020

System indices are needed by Elasticsearch and the stack so we should always be able to create them. Currently the action.auto_create_index setting governs whether any index can be auto created and could prevent system indices from being created. This behavior allows a user to unknowingly set a value for this setting that prevents the operation of certain features that are built-in to the product and adds to the steps needed to set up features and leads to frustration.

As part of the system indices effort we need to ensure that system indices can be automatically created from an index request.

@jaymode jaymode added >enhancement Team:Core/Infra Meta label for core/infra team labels Aug 27, 2020
@jaymode jaymode added the :Core/Infra/Core Core issues without another label label Aug 27, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Core)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >enhancement Team:Core/Infra Meta label for core/infra team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants