-
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
Create Migration Guide for 2.x to 5.x #1488
Comments
Config Migration TopbeatAll config options of topbeat were moved under its own topbeat namespace. Topbeat will still work with the old configuration but this will be removed in the next major release. To adjust your configuration, you have to take the following steps:
This will look similar to:
|
Config Migration PacketbeatAll config options of packetbeat were moved under its own packetbeat namespace. To keep packetbeat running, you must make the following modifications to your config file. Option 1
This will look as following:
Option 2
This will look as following:
|
Another topic is changing the URL used in your APT and Yum repo config. I don't think we've published 5.x to any package repos yet, but we will and the URL will be different. |
Move config settings from under |
It doesn't do yaml parsing, just line by line string operations. This means it is not able to transform any yaml syntax, but should work on the most common cases. On the plus side, it uses only python standard library modules and it keeps the comments as in the original file. Related to elastic#1488.
It doesn't do yaml parsing, just line by line string operations. This means it is not able to transform any yaml syntax, but should work on the most common cases. On the plus side, it uses only python standard library modules and it keeps the comments as in the original file. Related to #1488.
This can be closed as we now have migration guides. |
We have several backward compatibility breaks in 5.0. We should create a migration guide to make migration easier.
Please post below all the entries that should go into this migration guide.
The text was updated successfully, but these errors were encountered: