# Community Beat: Wrong version information in various make targets

**URL:** <https://discuss.elastic.co/t/community-beat-wrong-version-information-in-various-make-targets/69945>\
**Category:** Beats\
**Created:** [December 24, 2016, 5:07pm UTC](https://discuss.elastic.co/t/community-beat-wrong-version-information-in-various-make-targets/69945 "2016-12-24T17:07:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![christiangalsterer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christiangalsterer/32/6447_2.png) [@christiangalsterer](https://discuss.elastic.co/u/christiangalsterer)\
**Post date:** [December 24, 2016, 5:07pm UTC](https://discuss.elastic.co/t/community-beat-wrong-version-information-in-various-make-targets/69945/1 "2016-12-24T17:07:05Z")

</div>

When executing `make update` or `make package` for a community beat, the wrong version is used. Instead if using the version information from some place in the community beat, the version is read from ${ES\_BEATS}/dev-tools/packer/version.yml.

Due to this the version for the binary packages as well as in various generated template file is not the version of the community beat for the underlaying vendor version of beat.

See [https://github.com/christiangalsterer/httpbeat](https://github.com/christiangalsterer/httpbeat) and execute make update`or`make package` for an example.

I think it would be good ti implement a change which reads the version from a "well-known" place which can be configured/overwritten by the community beat, e.g. a file or as a property in the make file.

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [December 26, 2016, 3:10pm UTC](https://discuss.elastic.co/t/community-beat-wrong-version-information-in-various-make-targets/69945/2 "2016-12-26T15:10:54Z")

</div>

We recently had a [PR](https://github.com/elastic/beats/pull/3203) in that area. Were you proposing something similar?

---

<div class="post-metadata">

**Author:** ![christiangalsterer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christiangalsterer/32/6447_2.png) [@christiangalsterer](https://discuss.elastic.co/u/christiangalsterer)\
**Post date:** [December 26, 2016, 3:28pm UTC](https://discuss.elastic.co/t/community-beat-wrong-version-information-in-various-make-targets/69945/3 "2016-12-26T15:28:27Z")

</div>

Yes this was exactly I was looking for. Would be great to get this also merged in the 5.x branch.

---

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [December 26, 2016, 4:09pm UTC](https://discuss.elastic.co/t/community-beat-wrong-version-information-in-various-make-targets/69945/4 "2016-12-26T16:09:16Z")

</div>

For clarity do you need it in the 5.1 branch or in 5.x (we have both in git)? To 5.x it will happen in the first week of the next year. Let me know if you need it earlier.

---

<div class="post-metadata">

**Author:** ![christiangalsterer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christiangalsterer/32/6447_2.png) [@christiangalsterer](https://discuss.elastic.co/u/christiangalsterer)\
**Post date:** [December 26, 2016, 4:58pm UTC](https://discuss.elastic.co/t/community-beat-wrong-version-information-in-various-make-targets/69945/5 "2016-12-26T16:58:56Z")

</div>

I'm currently on 5.1.x so that would be my personal preference and early January is perfectly fine.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 14, 2017, 5:07pm UTC](https://discuss.elastic.co/t/community-beat-wrong-version-information-in-various-make-targets/69945/6 "2017-01-14T17:07:23Z")

</div>

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