Feat(eos_config_deploy_cvp): Allow the configlets_notes to be added from AVD
tgodaA opened this issue · comments
Enhancement summary
The configlets_notes variables is used in arista.cvp.cv_configlet_v3 module to set the Note on a configlet, which is set to default in the CVP collection. This variable can be passed from AVD when the arista.cvp.cv_configlet_v3 is called.
Which component of AVD is impacted
eos_config_deploy_cvp
Use case example
This has a potential benefit to set the version of network. This can be leveraged by big customers to know which version of configs they have provisioned currently.
Scenario1: We have observed that when a customer has to maintain multiple DataCenters with every DC being at it's own version of config release and multiple site configurations being released at once for a given DC (this is possible to save the development time as the provisioning can be done by a different team or a different member). Now it became hard to track the current state of the network. This notes in CVP configlets can be used to track the current state of a device.
Scenario2: In large DCs the development team and deployment team could be different. So production wouldn't know the state of the network if they have to check themselves as deployment might have not deployed the last release or releases due to some technical reason.
So, we can use this notes to comment the current state of the Switch that has been deployed last by providing certain version numbers as the value. For example, development team released a site config, let's say 1.2 (previous is 1.1), this number can be set in the configlets_notes to know if the 1.1 made it to the CVP or not.
Describe the solution you would like
Allow this variable to be set from AVD as a variable. cvp_configlets_notes: (default: 'Managed by Ansible')
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide
- I agree to follow this project's Code of Conduct