Open tchiapuziowong opened 2 years ago
Hi Tiffany...I realize that reaching out to you (here at github) isn't optimal, but I couldn't find your Aruba contact email-- great demo at ATM22 (locating Dan's water bottle) by the way. Say, regarding the modules at https://github.com/aruba/aoscx-ansible-collection/tree/master/docs. Are all of them to be used with REST API? I ask because though I know that aoscx_command & aoscx_config are to be used with "ansible_connection: network_cli", I wasn't sure about the other modules. Besides trial and error of each module, how can I identify which modules are to be used with "ansible_connection: httpapi" REST API, and which by CLI? I'm in the midst of using Ansible to configure many many 6400m AOS-CX switches, and it's been a great active learning experience. Thanks! I'll return to remove this message in a few days, because I'm unsure if it violates any github commenting guide lines. :)
Hi @TechFixer - Yes all modules except for aoscx_command and aoscx_config use REST API and therefore require the REST API inventory variables to be defined.
Here's our section that discusses how to us the SSH CLI modules.
A-ha...I thought so. Enormous thanks Tiffany! I've been diggin' deep with Ansible and AOS-CX v.10.08, and as an automation network engineer, I'm endeavoring to make the provisioning of 100s of 6400m switches more effecient beyond the method of purely CLI copy and paste. Believe or not, some of my cohorts still opt for that method.
Stay Healthy!
~Tony
From: tchiapuziowong @.> Sent: Monday, May 16, 2022 11:52 AM To: aruba/aoscx-ansible-collection @.> Cc: Tony @.>; Mention @.> Subject: Re: [aruba/aoscx-ansible-collection] AOS-CX Collection Doesn't Support Check Mode (Issue #25)
Hi @TechFixerhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTechFixer&data=05%7C01%7C%7C7cc4a396f3ad497682c708da376d304c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637883239357227815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sO4965hJrrZ%2BRdqJ6DAo%2FG3lqGvMbgph8uFaAW4HSMc%3D&reserved=0 - Yes all modules except for aoscx_command and aoscx_config use REST API and therefore require the REST API inventory variables to be defined.
Here's our sectionhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.arubanetworks.com%2Faruba-aoscx%2Fdocs%2Fusing-the-aos-cx-ansible-collection%23sshcli-modules&data=05%7C01%7C%7C7cc4a396f3ad497682c708da376d304c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637883239357227815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hjI24q1ytkEEQtr4vFQKuHoDMj76q8DcI%2F2gJOkajL8%3D&reserved=0 that discusses how to us the SSH CLI modules.
— Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Faruba%2Faoscx-ansible-collection%2Fissues%2F25%23issuecomment-1128019931&data=05%7C01%7C%7C7cc4a396f3ad497682c708da376d304c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637883239357227815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=24i6AZKmFw43S7MPB%2B7guEkI1NlsPRs5Tougs7LQZQQ%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOGSHZBU7CYTEWO6WK2NECTVKKKNXANCNFSM5VI7SRAA&data=05%7C01%7C%7C7cc4a396f3ad497682c708da376d304c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637883239357227815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tfgZu%2FIBCQG77GYL9ZbLJg%2BTF3a1jtCuzpdQ%2F9MqHrA%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
Any update on when / if this feature will be implemented?
@Jesse-Lee-Hughes This is something we've added into our backlog and currently do not have a date of delivery. Once it's been implemented/planned for release we'll update this issue.
Hi, i'ts been a few months - is this being worked on or still in the backlog?
Currently the CX collection doesn't support check mode in which it reports what changes would take place in the event the playbook would be executed.