--start-at-task seems to be fixed recently.
Thanks, Ansible devs! This is a major improvement to my daily workflow :-)
On Wednesday, December 2, 2015 at 4:10:17 PM UTC-8, Brian Coca wrote:
>
> Currently, this is the price we are paying for the dynamic 'task
> includes', we are looking for ways
Currently, this is the price we are paying for the dynamic 'task
includes', we are looking for ways around this issue but have not
found anything we are happy with yet.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubs
Thanks Brian.
Did you have a chance to talk to other devs? Is this a conversation I
could join in?
We've now switched internally to 2.0.0 but I'm finding a lot of debugging
much slower, as I have to use a mix of tags and temporary commenting-out to
get playbooks working.
Thanks,
-b
On Tues
I think they should 'just work' TM, but this is not a simple one,
having dynamic includes makes this an 'interesting' problem, checking
with other devs trying to figure this out.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
On Nov 30, 2015 11:48 PM, "Brian Coca" wrote:
>
> My tests included a role and a bunch of debug tasks in 2 plays, all
> worked, what did not have is a task include.
>
> This is probably due to the new 'dynamic' nature of tasks includes in
> 2.0, the same reason those tasks don't appear in task lis
My tests included a role and a bunch of debug tasks in 2 plays, all
worked, what did not have is a task include.
This is probably due to the new 'dynamic' nature of tasks includes in
2.0, the same reason those tasks don't appear in task lists.
--
Brian Coca
--
You received this message because
*Here's my minimal test case, which has one task.*
The task comes from an include, which seems to be the issue. Yes, roles
are great and we try to use them as much as possible, but our codebase has
a number of places where includes are used to define tasks lists.
Brian, please let me know wha
Brian, can you point me to the tests you're running?
As an update to the previous, I gave up on binary searching to find where
the behavior changed; the issue is present at v2.0.0-0.1.alpha1~250 but
before then I see a compilation issue where Ansible thinks quotes are
missing.
On Monday, Nove
Closed bugs don't normally get read.
If you can provide a minimally reproducible test case, we can look into it.
My tests show this feature working.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop rec
Thanks Brian. I roughly binary searched and the behavior seems to have
broken between Ansible code versions v1.9.4-1 and v2.0.0-0.1.alpha1.
Before, --list-tasks would show individual tasks and no 'meta' tasks. At
2.0, it just shows a shorter list of meta tasks, which breaks
--start-at-task.
the 'meta' tasks you see there might be the internal calls to `meta:
refresh_handlers` which don't normally have a name. List tasks in 2.0
shows these, they did not appear in previous versions.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible
[prior post had a link in the title - if a mod can delete that post, would
be great, thanks!]
I'm having some issues with ansible 2.0.0-stable (b69942a), where
--start-at-task can't find the task with that name.
I think a clue may be in --list-tasks, which doesn't list task names for
tasks d
12 matches
Mail list logo
