Upgrading libbeat and generated files


(Kevin Retzke) #1

What's the recommended procedure for upgrading the version of libbeat used by a beat? For point releases I expect just updating the vendored version will suffice, but what about major versions? Is there any way to update some of the generated files? Notably I see that sometime between 6.3.0 and 6.5.1 the build process has been moved to using mage, so there's some large changes there.


(Kevin Retzke) #2

Just a follow-up. I was able to successfully upgrade a beat from libbeat 6.3.0 to 6.5.1, by running generate.py over the existing beat location, then selectively committing the changes and discarding changes to the source and config files. I then ran:

rm -rf vendor/github.com/elastic
make copy-vendor
make update

I did this primarily because I was having some problems cross-compiling during make package but found the new make release works great.


(system) closed #3

This topic was automatically closed after 28 days. New replies are no longer allowed.