Feature: Validation of config using CloudVision

[chetryan]

Enhancement summary

At the moment, if AVD successfully generates device configuration, there is not guarantee that is correct for the device if the user supplied the wrong eos_designs or eos_cli_config_gen values. In the cases where CloudVision Portal is being used, CVP will validate the configlet against the device and report back any errors and warnings back to the user. This means that if there are errors or warnings, they are only visible onces the configlets on CVP have been changed. Any use of AVD in pipelines would not be ware that the generated configuration is not valid.

It would be great to have a feature in AVD (new role or addition to eos_config_deploy_cvp) to validate the configuration using existing CVP APIs before making any changes to configlets. This would allow:

• Validation of the generated configuration within pipelines/automation
• Keeps the configlets on CVP error-free at any point
• Enable use of templates/logic to search through errors/warnings etc.

Which component of AVD is impacted

others

Use case example

A typical use case would be:

• User makes changes to group_vars
• New configuration is generated by AVD run locally or in a pipeline
• New feature used to immediately validate the generated config against the devices.
• If errors and/or warnings are found, the playbook stops and generates a report.
• If no errors/warnings are found, playbook continues to upload the configlets to CVP.

Describe the solution you would like

The solution could either be a dedicate new role or an enhancement of eos_config_deploy_cvp and would be able to:

• Validate each config for each switch.
• Dump all the errors/warnings to csv/data file for processing by the user in other tasks
• Generate reports with summaries of duplicate/repeated errors and warnings
• Support variables to indicate whether or not to proceed if errors or warnings are encountered.

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

• [X] I agree to follow this project's Code of Conduct

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. The issue will be reviewed by a maintainer and may be closed