Hello, community, I am currently working on writing a new set of NetScaler collections for ansible. We already have a collection maintained at https://github.com/citrix/citrix-adc-ansible-modules
I would like to extend this OR entirely change it to better. NetScaler ADC under the hood is a FreeBSD OS and we have our own command prompt. I need to take care of three things - 1. collection modules for resources to configure the NetScaler device over NITRO (HTTP) 2. module/plugin (I am not sure) to directly give FreeBSD commands (bypassing the initial NS-CLI prompt). This is for general OS operations like `create directory`, `copy`, `tar/untar`, run some shell scripts etc. 3. module/plugin to directly give nscli such as `show version`, `add lb vserver` commands in the playbook to configure the NetScaler device. For points 2 and 3, we have a `ssh-connection-plugin` - https://github.com/citrix/citrix-adc-ansible-modules/blob/master/ansible-collections/adc/plugins/connection/ssh_citrix_adc.py For point 1, we have modules Now I see that there is a separate section in the Ansible documentation (https://docs.ansible.com/ansible/latest/network/dev_guide/index.html) Also, I see many plugins such as `httpapi`, `terminal`, `shell`, `network_cli` etc. - Can you please help to understand the difference between these? - What are the benefits I get if I choose `httpapi` plugin over our existing collection modules which uses ansible's `fetch_url` function? so that I can think of writing these plugins for our NetScaler ADC devices. Thanks in advance, Sumanth Lingappa -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/4828fb1f-2b31-4eb1-84f5-0bfbdda709d4n%40googlegroups.com.
