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
juniper.device collection and Python libraries version
N/A with Docs
OS / Environment
N/A with Docs
Summary
The documents refer to using a play level keyword of collection. This is not generally the recommended approach, instead using an Ansible FQCN is recommended, even if verbose at times. I think this is especially relevant here for potential name space issues, as well as mind tracking issues. It is not clear to the reader that config or software are specific to the juniper.device. The recommendation is to update documentation to reenforce that with documentation. As true with many of us in the open source world, I have far too many commitments to take this on, so no issues to close this with/without bias :)
Module Name
Ansible Collection
juniper.device collection and Python libraries version
OS / Environment
Summary
The documents refer to using a play level keyword of collection. This is not generally the recommended approach, instead using an Ansible FQCN is recommended, even if verbose at times. I think this is especially relevant here for potential name space issues, as well as mind tracking issues. It is not clear to the reader that
config
orsoftware
are specific to thejuniper.device
. The recommendation is to update documentation to reenforce that with documentation. As true with many of us in the open source world, I have far too many commitments to take this on, so no issues to close this with/without bias :)Steps to reproduce
N/A with docs
Expected results
Actual results
The text was updated successfully, but these errors were encountered: