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

[backport] PR #8391 to 5.0 #8444

Merged
merged 1 commit into from
Sep 22, 2016
Merged

[backport] PR #8391 to 5.0 #8444

merged 1 commit into from
Sep 22, 2016

Conversation

elastic-jasper
Copy link
Contributor

Backport PR #8391

Commit 1:
Don't try to delete index template along with pattern

This commit reverts a change to use the ingest API when deleting index
patterns via the Kibana UI. Back when I was building the Filebeat wizard
it made sense to try to delete any index templates or pipelines that may
have been created along with an index pattern. But now that we're only
shipping with CSV Upload, and we don't delete the actual indices that
CSV upload creates, it doesn't make much sense to delete the template.
Now we'll treate the indices and templates consistently.

This also fixes an issue where users would get a fatal error if they
were using Security and they didn't have permissions to delete
templates. Every index pattern deletion would also attempt to delete an
associated template, so if the user didn't have the correct permissions
they would get a 403.

Related: #6457

---------

**Commit 1:**
Don't try to delete index template along with pattern

This commit reverts a change to use the ingest API when deleting index
patterns via the Kibana UI. Back when I was building the Filebeat wizard
it made sense to try to delete any index templates or pipelines that may
have been created along with an index pattern. But now that we're only
shipping with CSV Upload, and we don't delete the actual indices that
CSV upload creates, it doesn't make much sense to delete the template.
Now we'll treate the indices and templates consistently.

This also fixes an issue where users would get a fatal error if they
were using Security and they didn't have permissions to delete
templates. Every index pattern deletion would also attempt to delete an
associated template, so if the user didn't have the correct permissions
they would get a 403.

Related: #6457

* Original sha: daa5b3b
* Authored by Matthew Bargar <[email protected]> on 2016-09-20T22:43:03Z
@Bargs Bargs merged commit 1fcde22 into 5.0 Sep 22, 2016
@epixa epixa deleted the jasper/backport/8391/5.0 branch September 27, 2016 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants