In the ET production environment there is one mega "ASYNC" release. Many unrelated products' Product Versions are associated with this release.
Let's make product_versions an optional parameter to errata_tool_release. This will make it easier to manage individual release-to-product-versions relationships with a separate yet-to-be-written errata_tool_release_product_versions Ansible module.
This is relevant to RHEL (uses "ASYNC" release) and OpenShift (uses "RHOSE ASYNC" release)
I've confirmed that I can delete all Product Versions from an existing release, so it should not be a problem to make it optional regardless of whether we're creating or editing a release. We'll default to creating the release with an empty PV list in the former case (creation), and we will not touch the existing PV list in the latter case (editing).
In the ET production environment there is one mega "ASYNC" release. Many unrelated products' Product Versions are associated with this release.
Let's make
product_versions
an optional parameter toerrata_tool_release
. This will make it easier to manage individual release-to-product-versions relationships with a separate yet-to-be-writtenerrata_tool_release_product_versions
Ansible module.This is relevant to RHEL (uses "ASYNC" release) and OpenShift (uses "RHOSE ASYNC" release)
I've confirmed that I can delete all Product Versions from an existing release, so it should not be a problem to make it optional regardless of whether we're creating or editing a release. We'll default to creating the release with an empty PV list in the former case (creation), and we will not touch the existing PV list in the latter case (editing).