You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Checking the Ontap CLI (version 9.14.1), there is no 'fireware' option.
The REST API documentation does show a 'cluster/firmware/history' API, which suggest that this Ansible documentation is a simple typo bug: cluster/fireware/history
rather than the correct parameter of: cluster/firmware/history
Component Name
na_ontap_rest_info
Ansible Version
N/A - documentation error
ONTAP Collection Version
N/A - documentation error
ONTAP Version
N/A - documentation error
Playbook
N/A - documentation error
Steps to Reproduce
N/A - documentation error
Expected Results
N/A - documentation error
Actual Results
N/A - documentation error
The text was updated successfully, but these errors were encountered:
Summary
Summary
There appears to be a typo in the documentation for Module 'na_ontap_rest_info' . The issue is with following argument for the 'gather_subset' parameter :
cluster/fireware/history
https://docs.ansible.com/ansible/latest/collections/netapp/ontap/na_ontap_rest_info_module.html#parameter-gather_subset
Issue Type
Documentation Report
Ansible Version
2.9 and 2.10
Component Name
na_ontap_rest_info
ONTAP Collection Version
22.12.0
Additional Information
Checking the Ontap CLI (version 9.14.1), there is no 'fireware' option.
The REST API documentation does show a 'cluster/firmware/history' API, which suggest that this Ansible documentation is a simple typo bug:
cluster/fireware/history
rather than the correct parameter of:
cluster/firmware/history
Component Name
na_ontap_rest_info
Ansible Version
N/A - documentation error
ONTAP Collection Version
N/A - documentation error
ONTAP Version
N/A - documentation error
Playbook
N/A - documentation error
Steps to Reproduce
N/A - documentation error
Expected Results
N/A - documentation error
Actual Results
N/A - documentation error
The text was updated successfully, but these errors were encountered: