Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

My customer is building a new SW-defined data center following Infrastructure as Code (IaC) principles. He would like to automate the installation and setup of virtual Nexus Dashboard.

For fully automating a ND deployment, various tasks and API requests are required for which there are no specific modules. For example:

• GET /v2/bootstrap/cluster - retrieve the serial number required as parameter for the nd_setup module (nd_setup with state 'query' uses /clusterstatus/install instead)
• GET /v2/clusterstatus/bootstrap - check the status of the initial bootstrap
• GET /sedgeapi/v1/k8s-mon/api/sehealth - check the status of the ND cluster
• GET /api/v1/release - retrieve release information
• GET /api/v1/servicepackage/cisco-ndfc/status - check the status of the service release
• etc.

Furthermore, ND deployment is evolving and required API requests are changing. Instead of creating new modules for every possibly required task, I suggest to create a generic module to flexibly sent REST API requests. Similar to the dcnm_rest module of the Cisco DCNM collection.

Example

- name: Check status of cluster bootstrap
  cisco.nd.nd_rest:
    method: GET
    path: /v2/clusterstatus/bootstrap

New or Affected Module(s)

• nd_rest

ND Version and ND Platform

• all

Collection Versions

• cisco.nd 1.2.0, 1.3.0