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
Based on my initial search, heres what i think the issue is
content_library_item_module missing
it looks like we expect the module to be generated but it was not generated. In the API spec, i noticed that the object key for content_library_item_module is listed twice, once with the post method and once with the get method. I think when we generated the modules, the content builder just went with the last defined object which happens to be the GET method.
vcenter_storage_policies_module missing
we dont generate this module, and dont expect it to be generated. Maybe we should, or just remove references to it
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
Summary
Now that the collection documentation is being generated on PR/MR, we can see that certain modules are referencing other modules that dont exist.
The workflow here provides the following warnings:
These warning messages are usually treated as failures. This behavior has been disabled in the workflow for now, but it should be re-enabled
These broken links cannot be updated in the modules themselves since the modules and the docs inside the modules are autogenerated from the API spec.
Issue Type
Documentation Report
Component Name
Validate Ansible Docs workflow
content_locallibrary_module
content_subscribedlibrary_module
vcenter_storage_policies_info_module
vcenter_vm_hardware_disk_module
vcenter_vm_module
vcenter_vm_storage_policy_module
Ansible Version
No response
Collection Versions
4.0.0-dev0
Configuration
$ ansible-config dump --only-changed
OS / Environment
No response
Additional Information
Based on my initial search, heres what i think the issue is
content_library_item_module
missingit looks like we expect the module to be generated but it was not generated. In the API spec, i noticed that the object key for
content_library_item_module
is listed twice, once with the post method and once with the get method. I think when we generated the modules, the content builder just went with the last defined object which happens to be the GET method.vcenter_storage_policies_module
missingwe dont generate this module, and dont expect it to be generated. Maybe we should, or just remove references to it
Code of Conduct
The text was updated successfully, but these errors were encountered: