Closed noredistribution closed 2 years ago
I would suggest to add a new keyword image_bundle
to the cv_container
schema and make sure it's not a required keyword so we don't introduce any breaking change.
Other option is to do a semi-breaking change, and have get_facts_v3 updated to change the image_bundle
key to match the imageBundle
in the schema.
That was the discussion on PR #505 - keep the schema as sacred...
We could still have get_facts_v3 output an image_bundle
key, for anyone that is already using it, but mark it as deprecated. whether or not it should be an optional keyword in the schema... ??
Issue Summary
In ansible-cvp 3.4.0 we've added some additional features around imageBundles and also started outputting if containers have image bundles assigned to them, e.g. when running cv_facts_3 the output will be like this:
the issue is that additional properties are not allowed in our schema
setting that to True will fix the issue and any possible future enhancements where this might happen: https://github.com/aristanetworks/ansible-cvp/blob/devel/ansible_collections/arista/cvp/plugins/module_utils/resources/schemas/v3.py#L241
Which component(s) of AVD impacted
cv_container_v3
How do you run AVD ?
Ansible CLI (with virtual-env or native python)
Input variables
Steps to reproduce
Relevant log output
Code of Conduct