-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add migration.enabled config option #9805
Conversation
e6be910
to
5a94aa8
Compare
@@ -63,7 +63,7 @@ import ( | |||
svc "github.com/elastic/beats/libbeat/service" | |||
"github.com/elastic/beats/libbeat/template" | |||
"github.com/elastic/beats/libbeat/version" | |||
"github.com/elastic/go-sysinfo" | |||
sysinfo "github.com/elastic/go-sysinfo" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like my idea / goimports did this automatically. Interesting.
Trying to add support to enable / disable aliases for the Kibana index pattern I stumbled over the following issue: #10013 Also opened elastic/kibana#28570 to get better support in Kibana. |
5a94aa8
to
141053a
Compare
141053a
to
6c0d37b
Compare
This PR will only address migration aliases for the Elasticsearch index template. A follow up PR will be created to also enable / disable it in Kibana index pattern after #10075 is done. |
84ea2bc
to
6c07d6d
Compare
This is ready for review. |
6c07d6d
to
46017b9
Compare
The migration.enabled config option is off by default. Enabling it will add all the alias fields which are used for making Beats 7.x data compatible with 6.x data for queries and dashboards. A user that upgrades can either set `migration.enabled: true` in the config file or run `-E migration.enabled=true` on the command line to also have the migration aliases in the Elasticsearch index template. Further changes: * Add system test to check the generated template * Fix autodiscovery tests. Were broken as probably the removal of the aliases by default did not work here as it relied on apache2.
fb1a3a5
to
dd782d1
Compare
The migration.enabled config option is off by default. Enabling it will add all the alias fields which are used for making Beats 7.x data compatible with 6.x data for queries and dashboards. A user that upgrades can either set `migration.enabled: true` in the config file or run `-E migration.enabled=true` on the command line to also have the migration aliases in the Elasticsearch index template. Further changes: * Add system test to check the generated template * Fix autodiscovery tests. Were broken as probably the removal of the aliases by default did not work here as it relied on apache2.
The migration.enabled config option is off by default. Enabling it will add all the alias fields which are used for making Beats 7.x data compatible with 6.x data for queries and dashboards.
A user that upgrades can either set
migration.enabled: true
in the config file or run-E migration.enabled=true
on the command line to also have the migration aliases in the Elasticsearch index template.Further changes: