Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the documentation for the
device_discovery
backend and the Git configuration manager. The changes enhance clarity, add new supported defaults, and provide additional examples for configuration. Below is a summary of the most important changes:Updates to
device_discovery
documentation:VLAN
as a supported entity in thedevice_discovery
backend, with a link to its documentation. (docs/backends/device_discovery.md
)if_type
(interface type),role
,tenant
, andvrf
forIP address
andPrefix
entities, as well as a comprehensive set of defaults forVLAN
entities. (docs/backends/device_discovery.md
) [1] [2]vlan
settings under thedefaults
section. (docs/backends/device_discovery.md
)Updates to Git configuration documentation:
config_manager
andbackends
sections must be passed directly to the agent at startup since they are not dynamically reconfigurable. (docs/configs/git.md
)backends
configuration examples fornetwork_discovery
anddevice_discovery
. (docs/configs/git.md
)policy.yaml
file, demonstrating how to declare the backend it applies to and configure schedules, defaults, and scope fordevice_discovery
. (docs/configs/git.md
)