# Community.beszel - Ansible Collection

**URL:** <https://forum.ansible.com/t/community-beszel-ansible-collection/43999>\
**Category:** Project Discussions\
**Tags:** coll-repo-request, beszel\
**Created:** [July 22, 2025, 6:49pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999 "2025-07-22T18:49:32Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [July 22, 2025, 6:49pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/1 "2025-07-22T18:49:32Z")

</div>

Hi folks,

I’ve been maintaining an Ansible [role](https://github.com/dbrennand/ansible-role-beszel) for [Beszel](https://beszel.dev/) and recently someone submitted a [PR](https://github.com/dbrennand/ansible-role-beszel/pull/10) which ideally should be a separate role, and I already had an idea a few months ago for creating an Ansible collection for Beszel, so in the future I could create some modules for adding new devices as well as roles for deploying the Hub and Agent.

I opened a [GitHub discussion](https://github.com/henrygd/beszel/discussions/969) and the author is happy for a collection to be created.

Could a collection for Beszel in the community namespace be created?

Thanks and have a great evening.

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [July 29, 2025, 5:05pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/2 "2025-07-29T17:05:14Z")

</div>

Hi @gundalow - What do you think? 🙂

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 29, 2025, 6:47pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/3 "2025-07-29T18:47:38Z")

</div>

@dbrennand Thanks for the 2nd ping 🙂

[GitHub - ansible-collections/community.beszel](https://github.com/ansible-collections/community.beszel) created

Please [accept the invite](https://github.com/ansible-collections/community.beszel/invitations) to the repo.

@Andersson007 Can you setup this new repo in Zuul (assuming we are still using that Collection publishing)

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [August 20, 2025, 6:31am UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/4 "2025-08-20T06:31:10Z")

</div>

Hi @gundalow @Andersson007

`community.beszel` `0.1.0` [PR](https://github.com/ansible-collections/community.beszel/pull/1) is ready. What is the process for getting it reviewed seeing as I’m the only maintainer. Do one of you review it?

All the GitHub Action workflows for Ansible Lint, Molecule and Ansible tests are passing.

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [August 25, 2025, 5:40pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/5 "2025-08-25T17:40:06Z")

</div>

Hey @felixfontein - Are you be able to advise here? 🙂

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 25, 2025, 7:24pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/6 "2025-08-25T19:24:06Z")

</div>

@dbrennand if you have commit rights, simply press the big green Merge button 🙂 If you’re the only maintainer, and nobody else seems to be interested in reviewing things in the collection, that’s usually the only way forward.

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [August 26, 2025, 7:12am UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/7 "2025-08-26T07:12:33Z")

</div>

@dbrennand hello, sorry for the late response, I’m just back from a long PTO.  
I’ve just added the collection to Zuul: it’ll publish the collection automatically when it sees a new tag, please use the [Releasing guidelines](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_release_without_branches.html) to release the collection.

You might be also interested in reading:

- [Maintainer guidelines](https://docs.ansible.com/ansible/latest/community/maintainers.html): covers more than just releasing.
- [Collection inclusion requirements](https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html): in case you want to submit the collection for inclusion to the package in future (must contain modules and plugins). The sooner you adopt the requirements the fewer things you need to change in future.
- [How to write a simple module post](https://forum.ansible.com/t/how-to-create-an-ansible-collection-with-a-simple-module-step-by-step/9718): you can use it as a skeleton for your first module if you don’t have any yet.

Thanks

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [August 26, 2025, 7:29am UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/8 "2025-08-26T07:29:29Z")

</div>

Thanks @Andersson007 - those links are very helpful 🙂

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [September 2, 2025, 12:27pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/9 "2025-09-02T12:27:10Z")

</div>

@dbrennand FYI, I’ve setup branch protections (PRs required, though you can self-merge)

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [September 2, 2025, 12:27pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/10 "2025-09-02T12:27:55Z")

</div>

@dbrennand Could you please announce the new collection in the Bullhorn, thanks

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [September 2, 2025, 12:55pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/11 "2025-09-02T12:55:24Z")

</div>

Do you have a link on how to do that? I’ve lost the link that someone else sent me. 😔

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [September 2, 2025, 1:20pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/12 "2025-09-02T13:20:34Z")

</div>

To share a news item for the Bullhorn, go into the Ansible social room on Matrix at [#social:ansible.com](https://matrix.to/#/#social:ansible.com). You can then tag newsbot with @newsbot at the start of your update. An editor will then review and approve your item before including it in the next edition!

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [September 2, 2025, 8:53pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/13 "2025-09-02T20:53:05Z")

</div>

Hi @gundalow

Something is not right, I can no longer push any commits to my feature branch which has a PR created 😕

```auto
remote: error: GH013: Repository rule violations found for refs/heads/0.3.0.        
remote: Review all repository rules at https://github.com/ansible-collections/community.beszel/rules?ref=refs%2Fheads%2F0.3.0        
remote: 
remote: - Changes must be made through a pull request.        
remote: 
To github.com:ansible-collections/community.beszel.git
 ! [remote rejected] 0.3.0 -> 0.3.0 (push declined due to repository rule violations)
error: failed to push some refs to 'github.com:ansible-collections/community.beszel.git'

```

So I no longer have direct commit access to the repository anymore?

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [September 3, 2025, 7:28am UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/14 "2025-09-03T07:28:31Z")

</div>

@dbrennand ~~it says you should 1. create a branch locally from updated main 2. commit your changes 3. push to your github fork 4. open a PR and merge it. Don’t push directly to your upstream branch - it’s a fundamental rule there.  
See the [Quick-start PR guide](https://docs.ansible.com/ansible/devel/community/create_pr_quick_start.html) for step-by-step guidance~~

Sorry for the noise, i should’ve read messages more carefully…  
Thanks

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [September 3, 2025, 9:20am UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/15 "2025-09-03T09:20:41Z")

</div>

I’ve changed the branch protections so they only apply to main.

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [September 3, 2025, 7:08pm UTC](https://forum.ansible.com/t/community-beszel-ansible-collection/43999/16 "2025-09-03T19:08:35Z")

</div>

Great, thank you 🙂
