+3
Hello,
I have started to create an Ansible Collection for the Veeam Backup & Replication RestAPI. It's more like a PoC and I need to complain that my python skills are bad.
In the case anyone is interrested in collobarting for this project, feel free to contact me.
Current state:
https://github.com/vMarkusK/veeam_rest-ansible
Best wishes
Markus
+17
Intetesting, I will have a look at it. 😎👍🏼
+7
Definitely interested
+2
I can jump in on this if I can find some time.
I am finishing out some other projects, starting a book, and helping
+3
+14
I know
+8
Interesting work, thank you for sharing
+5
I’m currently in the process of updating the collection to support v12 so everyone can use it to hit the ground running when it’s released! 😎
+3
I’m currently in the process of updating the collection to support v12 so everyone can use it to hit the ground running when it’s released! 😎
I don't think merging these two collections is a good idea.
- Mix of PowerShell and Python based modules.
- Different use cases, infra lifecycle with native PS Module and VBR operations via RestAPI.
However, I would like to see the modul moved to the VeeamHub. I already uses this namespace
+3
Interesting work, thank you for sharing
Do you think that will happen?
It is more likely that RedHat itself will jump on, as it is the case with the vmware_rest Collection.
+5
Understood. However, I’ll say that Ansible collections were designed so that all modules, roles, and sample playbooks of a product could be listed in a single collection versus having multiple disparate projects. What’s outlined here wouldn’t conflict/duplicate already existing content as the aforementioned collection is geared only towards Install/Patch/Upgrade and not configuring the software.
However, I would like to see the module moved to the VeeamHub.
If you change your mind, I’d be happy to host these modules within Ansible collection in the modules folder:
https://github.com/VeeamHub/veeam-ansible/tree/master/plugins/modules
+3
Understood. However, I’ll say that Ansible collections were designed so that all modules, roles, and sample playbooks of a product could be listed in a single collection versus having multiple disparate projects. What’s outlined here wouldn’t conflict/duplicate already existing content as the aforementioned collection is geared only towards Install/Patch/Upgrade and not configuring the software.
However, I would like to see the module moved to the VeeamHub.
If you change your mind, I’d be happy to host these modules within Ansible collection in the modules folder:
https://github.com/VeeamHub/veeam-ansible/tree/master/plugins/modules
I will think about it
+3
https://github.com/vMarkusK/veeam-ansible/tree/merge
Changes based on the merge have not yet been fully tested. Just looking for early feedback.
+5
That’s exactly where I saw the modules. Instead of the documentation added to the main README, I was planning on this information going in the docs directory (doesn’t exist currently). The documentation for the current role in this collection would be moved as well.
This would bring things more in line with Ansible’s defined collection structure and would make it more easy to consume via Ansible Galaxy.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
