New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make using blocks as handlers a parser error #79993
Conversation
Fixes ansible#79968 ci_complete
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.
This looks fine to me, but I simultaneously question whether there is technically a bug in _get_next_task_from_state
since it is returning something that is not a Task
. Or maybe that task is just poorly named at this point. In either case, this change is fine on its own.
Normally if a state sees a block it recursively enters a new nested state and takes a task from that block. Since we don't support that for handlers we could, in addition to this PR, also raise an assertion error if/when |
Yep, like I said, I'm good with the current state of this PR, but maybe something to look at in the future. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Fixes ansible#79968 (cherry picked from commit bd329dc)
Fixes ansible#79968 (cherry picked from commit bd329dc)
SUMMARY
Fixes #79968
ci_complete
ISSUE TYPE
COMPONENT NAME
lib/ansible/playbook/helpers.py