Utilizing "data_path:metadata.platform" to dynamically generate platform entry tags as part of cv_tags for the devices.

[Spandanaarista]

Enhancement summary

Leveraging structured_config to dynamically generate tag entries is highly beneficial. However, I'm wondering if we can incorporate the platform into it as well. Currently, the following configuration is not working as expected:

generate_cv_tags:
device_tags:
- name: hardware
data_path: metadata.platform

Which component of AVD is impacted

eos_designs

Use case example

Pushing user tags from AVD to CVP for use in "Software Management Studio" can leverage dynamic fields instead of manually creating everything. The platform tag, in particular, can be highly useful for distinguishing between 32-bit and 64-bit platforms.

Describe the solution you would like

As @ClausHolbechArista , mentioned : The metadata is created after/around the logic that creates the cv_tags, so we cannot read the metadata here since it is not created yet. We could look into modifying the ordering to generate the tags after all the other metadata.

Describe alternatives you have considered

Creating user tags for all hosts by manually adding them.

Additional context

@ClausHolbechArista

Contributing Guide

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