# devtools.UseCommunityBeatPackaging() has gone missing

**URL:** <https://discuss.elastic.co/t/devtools-usecommunitybeatpackaging-has-gone-missing/353201>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [February 13, 2024, 6:51pm UTC](https://discuss.elastic.co/t/devtools-usecommunitybeatpackaging-has-gone-missing/353201 "2024-02-13T18:51:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lasse\_Johnsen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lasse_johnsen/32/131698_2.png) [@Lasse\_Johnsen](https://discuss.elastic.co/u/Lasse_Johnsen)\
**Post date:** [February 13, 2024, 6:51pm UTC](https://discuss.elastic.co/t/devtools-usecommunitybeatpackaging-has-gone-missing/353201/1 "2024-02-13T18:51:46Z")

</div>

At Timebeat we build a community beat. It would be great to see more support for this reintroduced. Most if not all community beats have seen no development in 2-3 years except ours.

I've noticed that in the latest version we get the error :  
Error: no package specs are registered. Call UseCommunityBeatPackaging, UseElasticBeatPackaging or USeElasticBeatWithoutXPackPackaging first.

However the UseCommunityBeatPackaging function has been removed. So we now we reimplement it in our magefile.go ourselves by calling:

```
    const packageSpecFile = "dev-tools/packaging/packages.yml"
    devtools.MustUsePackaging("community_beat", packageSpecFile)

```

Is this a bug or the preferred approach now? At least having an error message suggesting calling a function that has been removed seems like a bug.

---

<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:** [March 12, 2024, 8:51pm UTC](https://discuss.elastic.co/t/devtools-usecommunitybeatpackaging-has-gone-missing/353201/2 "2024-03-12T20:51:53Z")

</div>

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