[es-archiver] Use alias for Kibana mappings #101537
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In 7.x, when saved objects point to an index and not an alias it will assume it's pre-6.8 and perform a legacy migration. This causes issues with the removal of oss builds. This update prevents that from happening by using an alias. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
|
Jenkins, test it |
tylersmalley
force-pushed
the
es-archives-kbn-alias-no-data
branch
from
5a1455b to
44c6dad
Compare
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
tylersmalley
added
v7.14.0
v8.0.0
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
I guess if we create any new es_archives for Kibana we would need to manually change from the index to an alias? |
|
@LeeDr Saving an esArchive for a Kibana index will actually include the alias. I assume these ones were just really old. Soon we won't allow esArchives to manipulate the Kibana index. |
jbudz
approved these changes
Jun 8, 2021
TinaHeiligers
approved these changes
Jun 8, 2021
tylersmalley
added
the
auto-backport
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 8, 2021
In 7.x, when saved objects point to an index and not an alias it will assume it's pre-6.8 and perform a legacy migration. This causes issues with the removal of oss builds. This update prevents that from happening by using an alias. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
tylersmalley
pushed a commit
that referenced
this pull request
Jun 8, 2021
In 7.x, when saved objects point to an index and not an alias it will assume it's pre-6.8 and perform a legacy migration. This causes issues with the removal of oss builds. This update prevents that from happening by using an alias. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co> Co-authored-by: Tyler Smalley <tyler.smalley@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In 7.x, when saved objects point to an index and not an alias it will
assume it's pre-6.8 and perform a legacy migration. This causes issues
with the removal of oss builds. This update prevents that from happening
by using an alias.