-
Notifications
You must be signed in to change notification settings - Fork 35
Don't require in-line play text to start with list #362
Don't require in-line play text to start with list #362
Conversation
See the following thread for reference: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bshephar, rabi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
In the commit message you wrote |
f260711
to
1aef24f
Compare
New changes are detected. LGTM label has been removed. |
5a21fd2
to
33d3331
Compare
This change removes the webhook validation requirement that in-line plays need to be lists. A play in Ansible is a dict, while a playbook is a list of plays. This change ensures we validate on the play format to conform with the terminology in use. For reference, see: https://github.com/ansible/ansible/blob/10f9b8e6554e024e3561170153b8e7fde5e7e4fb/test/units/playbook/test_play.py#L48 Given the terminology we use in the OpenStackDataPlaneService of 'play', we should then validate on the Ansible defined 'play' format, rather than a 'playbook' format. Signed-off-by: Brendan Shephard <[email protected]>
33d3331
to
4c4ca5a
Compare
@bshephar: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/ed580333ea79457e9b82f4034af7345f ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 42m 36s |
Need to change the repo-setup service in CI to keep this moving now:
|
The 'Play' field of the OpenStackDataPlaneService is intended to accept an Ansible play rather than a playbook. This change aligns that requirement with: openstack-k8s-operators/openstack-ansibleee-operator#362 Signed-off-by: Brendan Shephard <[email protected]>
recheck |
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/452320578fc140dcbe9b0acbe7356d4f ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 06m 27s |
The more I think about this, the more I think we shouldn't change it. It's nice to be able to provide an entire in-line playbook. Even if the terminology isn't technically correct, I think I prefer the functionality if we just allow users to provide entire playbooks. |
I'm closing this. We need to change the terminology rather than the implementation. We pass this to the |
This change removes the webhook validation requirement that in-line plays need to be lists. A play in Ansible is a dict, while a playbook is a list of plays. This change ensures we validate on the play format to conform with the terminology in use. For reference, see: https://github.com/ansible/ansible/blob/devel/test/units/playbook/test_play.py\#L48
Given the terminology we use in the OpenStackDataPlaneService of 'play', we should then validate on the Ansible defined 'play' format, rather than a 'playbook' format.
Depends-On: openstack-k8s-operators/install_yamls#835