Skip to content

Revert "Introduce system index APIs for Kibana (#52385)" #53912

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

Merged
merged 4 commits into from
Mar 23, 2020

Conversation

rjernst
Copy link
Member

@rjernst rjernst commented Mar 20, 2020

This mostly reverts commit 4c0e8f1.

It should be re-added once #53909 is addressed.

This reverts commit 4c0e8f1.

It should be re-added once elastic#53909 is addressed.
@rjernst rjernst added >non-issue :Core/Infra/Core Core issues without another label v8.0.0 v7.7.0 labels Mar 20, 2020
@elasticmachine
Copy link
Collaborator

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

rjernst added a commit to rjernst/elasticsearch that referenced this pull request Mar 21, 2020
@Tim-Brooks
Copy link
Contributor

Thanks for this @rjernst

@rjernst rjernst merged commit 8264bdd into elastic:master Mar 23, 2020
@rjernst rjernst deleted the revert_system_indices_threadcontext branch March 23, 2020 16:11
rjernst added a commit that referenced this pull request Mar 23, 2020
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Mar 23, 2020
rjernst added a commit that referenced this pull request Mar 23, 2020
jaymode added a commit to jaymode/elasticsearch that referenced this pull request Apr 7, 2020
This change reintroduces the system index APIs for Kibana wihtout the
changes made for marking what system indices could be accessed using
these APIs. In essence, this is a partial revert of elastic#53912. The changes
for marking what system indices should be allowed access will be
handled in a separate change.

The APIs introduced here are wrapped versions of the existing REST
endpoints. A new setting is also introduced since the Kibana system
indices' names are allowed to be changed by a user in case multiple
instances of Kibana use the same instance of Elasticsearch.

Relates elastic#52385
jaymode added a commit that referenced this pull request Apr 8, 2020
This change reintroduces the system index APIs for Kibana without the
changes made for marking what system indices could be accessed using
these APIs. In essence, this is a partial revert of #53912. The changes
for marking what system indices should be allowed access will be
handled in a separate change.

The APIs introduced here are wrapped versions of the existing REST
endpoints. A new setting is also introduced since the Kibana system
indices' names are allowed to be changed by a user in case multiple
instances of Kibana use the same instance of Elasticsearch.

Relates #52385
jaymode added a commit to jaymode/elasticsearch that referenced this pull request Apr 8, 2020
This change reintroduces the system index APIs for Kibana without the
changes made for marking what system indices could be accessed using
these APIs. In essence, this is a partial revert of elastic#53912. The changes
for marking what system indices should be allowed access will be
handled in a separate change.

The APIs introduced here are wrapped versions of the existing REST
endpoints. A new setting is also introduced since the Kibana system
indices' names are allowed to be changed by a user in case multiple
instances of Kibana use the same instance of Elasticsearch.

Relates elastic#52385
jaymode added a commit that referenced this pull request Apr 8, 2020
This change reintroduces the system index APIs for Kibana without the
changes made for marking what system indices could be accessed using
these APIs. In essence, this is a partial revert of #53912. The changes
for marking what system indices should be allowed access will be
handled in a separate change.

The APIs introduced here are wrapped versions of the existing REST
endpoints. A new setting is also introduced since the Kibana system
indices' names are allowed to be changed by a user in case multiple
instances of Kibana use the same instance of Elasticsearch.

Relates #52385
Backport of #54858
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.

5 participants