Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle task name interpolation #16

Closed
louisquentinjoucla opened this issue Jun 13, 2022 · 1 comment 路 Fixed by #17
Closed

Handle task name interpolation #16

louisquentinjoucla opened this issue Jun 13, 2022 · 1 comment 路 Fixed by #17

Comments

@louisquentinjoucla
Copy link
Contributor

louisquentinjoucla commented Jun 13, 2022

Hi everyone 馃憢 ,

With Ansible you are able to interpolate task name in certain circumstances.
One is when you use include_tasks, you are able to interpolate your tasks name in the included file like the following:

---

- name: "Echo {{ include_message }}"
  shell: "echo {{ include_message }}"

Unfortunately the task name is not yet interpolated in hook v2_runner_on_start for linear strategy, which cause B event to have a different name than the E event. As the E & B events name differs, the end is not catch, here is an example:

image

Fortunately v2_playbook_on_task_start hook (which is triggered before v2_runner_on_start) returns the interpolated name. We could use that.

@mhansen
Copy link
Owner

mhansen commented Jun 16, 2022

Oh, neat. Thanks for spotting this, yes let's get this fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants