Community.beszel - Ansible Collection

Project Discussions
,
1

Hi folks,

I’ve been maintaining an Ansible role for Beszel and recently someone submitted a PR 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 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.

2

Hi @gundalow - What do you think? :slightly_smiling_face:

3

@dbrennand Thanks for the 2nd ping :slight_smile:

GitHub - ansible-collections/community.beszel created

Please accept the invite to the repo.

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

1 Like
4

Hi @gundalow @Andersson007

community.beszel 0.1.0 PR 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.

5

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

6

@dbrennand if you have commit rights, simply press the big green Merge button :slight_smile: 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.

2 Likes
7

@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 to release the collection.

You might be also interested in reading:

Thanks

1 Like
8

Thanks @Andersson007 - those links are very helpful :slightly_smiling_face:

1 Like
9

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

1 Like
10

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

11

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

12

To share a news item for the Bullhorn, go into the Ansible social room on Matrix at #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!

1 Like
13

Hi @gundalow

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

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?

14

@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 for step-by-step guidance

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

15

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

1 Like
16

Great, thank you :slightly_smiling_face:

1 Like