This is in reference to this question that was raised on the NSO developer hub forum:
https://community.cisco.com/t5/nso-developer-hub-discussions/using-ansible-quot-nso-action-quot-module-to-invoke-quot-load/m-p/4173500

The following line validates that the input key is a YANG child in the schema of the input container but for a choice this is not correct and the correct input is being rejected:

It looks like this collection is effectively unmaintained. According to the current community guidelines for collections, we will consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: cisco.nso for more information.

At least one month after this announcement appears here and on Bullhorn, the Ansible community engineering steering committee will vote on whether this collection is considered unmaintained and will be removed, or whether it will be kept. If it will be removed, this will happen earliest in Ansible 9.0.0. Please note that people can still manually install the collection with ansible-galaxy collection install mellanox.onyx even when it has been removed from Ansible.

with NSO5.4 a "rollback-id" is available in json-rpc API. when conforming a config, the module should return this ID that could be used later in the playbook to rollback changes.

Similarly, commoit-queue-id would help the playbook to monitor the execution of the commit-queue item.

Hi! The Ansible Community Steering Committee has determined that this collection does not tag its releases in its git repository. This violates the repository management section of the Collection Requirements:

Every collection MUST have a public git repository. Releases of the collection MUST be tagged in said repository. This means that releases MUST be git taged and that the tag name MUST exactly match the Galaxy version number. Tag names MAY have a v prefix, but a collection's tag names MUST have a consistent format from release to release.
Additionally, collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release. Any changes made during the build process MUST be clearly documented so the collection artifact can be reproduced.

Note that this requirement has recently been clarified, but its intent remains the same. Please tag at least the previous 1-2 releases of your collection to come into compliance.

Please keep us updated and let us know if you have any questions. Thanks!

I was looking at this collcetion a bit. I have some questions/points:

1. example in https://github.com/CiscoDevNet/ansible-nso/blob/master/plugins/modules/nso_verify.py does not use FQCN
2. what's https://github.com/CiscoDevNet/ansible-nso/tree/master/tests/sanity/unused_ignores ?
3. do you have a CI running at least the sanity tests with ansible-base's stable-2.10 and devel branches?

Besides that, LGTM.

CC @gundalow @abadger

Based on the community decision to use true/false for boolean values in documentation and examples, we ask that you evaluate booleans in this collection and consider changing any that do not use true/false (lowercase).

See documentation block format for more info (specifically, option defaults).

If you have already implemented this or decide not to, feel free to close this issue.

P.S. This is auto-generated issue, please raise any concerns here

feedback from user:

User is working on a compliance check where they use Ansible module to interact with NSO’s compliance templates. The challenge is we only could figure out how to save the results to the state directory with the html results. This has been difficult because we want to GET the results form the API to pass to Ansible.

I have a task to run the compliance report but there doesn't seem to be a great way to get the report itself from the API?
Right now, the script just looks to see if there were any violation errors and if there are, it will re-apply the template
It would be best if a preview of what the compliance report violations are could be added to the script. Trying to use the URI module to download that report like a web page could be awkward.
I had to write a small module to attach a device template in NSO as the nso_action ansible module didn't seem to be able to handle it correctly. This could be a bug in the ansible module.

SUMMARY

Dear maintainers,

This is important for your collections!

• In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that will be closed soon.

  • To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page.
  • If you do not want to get notifications about related discussions, please subscribe only to Issues.
  • Please read the brief guidelines on how the repository should be used.
  • Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!

• Also we would like to remind you about the Bullhorn contributor newsletter which has recently started to be released weekly. To learn what it looks like, see the past releases. Please subscribe and talk to the Community via Bullhorn!

• Join us in #ansible-social (for news reporting & chat), #ansible-community (for discussing collection & maintainer topics), and other channels on Matrix/IRC.

• Help the Community and the Steering Committee to make right decisions by taking part in discussing and voting on the Community Topics that impact the whole project and the collections in particular. Your opinion there will be much appreciated!

Thank you!

When performing a commit in NSO, you need to be able to set the commit flags like "no-networking", "commit-queue", etc.