OK. Yet again, thanks for the help.
Op vrijdag 27 december 2013 19:52:03 UTC+1 schreef Michael DeHaan:
>
> Doesn't matter as it is for playbooks.
>
> -- Michael
>
> On Dec 27, 2013, at 1:35 PM, TextEditor >
> wrote:
>
> Seems logical. Can you maybe explain why it worked in 1.3 on task files?
>
>
OK. Yet again, thanks for the help.
Op vrijdag 27 december 2013 19:52:03 UTC+1 schreef Michael DeHaan:
>
> Doesn't matter as it is for playbooks.
>
> -- Michael
>
> On Dec 27, 2013, at 1:35 PM, TextEditor >
> wrote:
>
> Seems logical. Can you maybe explain why it worked in 1.3 on task files?
>
>
Doesn't matter as it is for playbooks.
-- Michael
On Dec 27, 2013, at 1:35 PM, TextEditor wrote:
Seems logical. Can you maybe explain why it worked in 1.3 on task files?
Op vrijdag 27 december 2013 15:21:58 UTC+1 schreef Michael DeHaan:
>
> This command is only intended for running on the top
And that one does work with 1.4:
ansible-playbook --syntax-check --list-tasks -i tests/ansible_hosts
./playbooks/default-vps-setup.yml
[...]
ERROR: Syntax Error while loading YAML script,
/home/remy/ansible/playbooks/roles/vim/tasks/main.yml
Note: The error may actually appear before this posi
Seems logical. Can you maybe explain why it worked in 1.3 on task files?
Op vrijdag 27 december 2013 15:21:58 UTC+1 schreef Michael DeHaan:
>
> This command is only intended for running on the top level playbook. It
> is not intended for running directly on task files which are by definition
>
This command is only intended for running on the top level playbook. It is
not intended for running directly on task files which are by definition not
playbooks.
-- Michael
On Dec 27, 2013, at 2:16 AM, TextEditor wrote:
It is run on the YAML files because when run on just the playbook which
in
Sorry, I forgot to mention, when looking through the code, I realized in order
to get it to check all the roles too, you need to use the --list-tasks argument
too:
ansible-playbook --syntax-check --list-tasks site.yml
--
Matt Martz
m...@sivel.net
On December 27, 2013 at 8:05:50 AM, TextEditor
Even when a broken playbook or a broken yaml file is includes as role it
validates as correct with 1.4.
Op vrijdag 27 december 2013 08:16:26 UTC+1 schreef TextEditor:
>
> It is run on the YAML files because when run on just the playbook which
> includes the roles it does not check the includes r
I can clearly reproduce it with my set of playbooks here. Did you try it
with the playbook in the ticket? As in, the playbook and the vim role. That
alone gives the error on 1.4 and not on 1.3.
Op vrijdag 27 december 2013 01:01:52 UTC+1 schreef Michael DeHaan:
>
> Saw your ticket, as stated, it
It is run on the YAML files because when run on just the playbook which
includes the roles it does not check the includes roles.
And, as also can be seen in the ticket, checking of all the YAML files with
Ansible 1.3 did work just fine.
Op vrijdag 27 december 2013 02:23:52 UTC+1 schreef Matt
I believe the issue is that you are running a --syntax-check against something
that is not a playbook. The error message actually states that as well:
"ERROR: apt is not a legal parameter in an Ansible Playbook”
And that is a correct error, as ‘apt’ is not a legal parameter in a playbook.
>Fro
Saw your ticket, as stated, it could not be reproduced.
-- Michael
On Dec 26, 2013, at 6:50 PM, TextEditor wrote:
Since my bug report is ignored and closed I'm asking for support here.
Since the upgrade to Ansible 1.4 the --syntax-check feature broke when used
with role files.
This is the tick
Since my bug report is ignored and closed I'm asking for support here.
Since the upgrade to Ansible 1.4 the --syntax-check feature broke when used
with role files.
This is the ticket: https://github.com/ansible/ansible/issues/5412
--syntax-check fails on 1.4.with ERROR: MODULE is not a legal p
13 matches
Mail list logo
