-
Epic
-
Resolution: Done
-
Normal
-
rhos-18.0.0
-
None
-
OpenStackDataPlaneService Play field expects a Playbook not a Play
-
False
-
-
False
-
?
-
?
-
?
-
?
-
0% To Do, 0% In Progress, 100% Done
-
Automated
-
-
-
2023Q3
-
Moderate
Description:
When creating a custom OpenStackDataPlaneService and leveraging the `Play` field. The field validation tries to validate for an Ansible playbook rather than a Play.
A play is a Dictionary as per:
https://github.com/ansible/ansible/blob/10f9b8e6554e024e3561170153b8e7fde5e7e4fb/test/units/playbook/test_play.py#L48
Reproducer:
Doesn't work with a Play:
https://github.com/openstack-k8s-operators/dataplane-operator/pull/871#discussion_r1610829807
Does work with a Playbook:
https://github.com/openstack-k8s-operators/dataplane-operator/pull/871#discussion_r1610831535
Expected behavior:
The validation should validate a Play instead of a Playbook and accept valid Plays.
- account is impacted by
-
OSPRH-7241 Webhook should validate for a Ansible Play instead of Playbook
-
- Closed
-
-
OSPRH-7242 Change description of Play object in OpenStackDataPlaneService
-
- Closed
-
-
OSPRH-7547 Rename dataplane-operator Play field
-
- Closed
-
- clones
-
OSPRH-7240 OpenStackDataPlaneService Play field expects a Playbook not a Play
-
- Closed
-