in current ansible stable's template:
if not self.runner.is_playbook:
raise errors.AnsibleError("in current versions of ansible,
templates are only usable in playbooks")
I was looking of ways around this to allow for users to actually use
template ad-hoc, i was thinking of ch
On Monday, June 29, 2015 at 5:51:15 AM UTC-7, Brian Coca wrote:
>
> fact gathering is one issue I see, off the bat. The template module is
> hardcoded to error on adhoc, because of this.
>
I'm not following. Can you elaborate on this?
--
You received this message because you are subscribed to
fact gathering is one issue I see, off the bat. The template module is
hardcoded to error on adhoc, because of this.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails f
Interesting.
Not sure what the impediments are. It would certainly make Galaxy
testing easier, though.
H.
On Sun, Jun 28, 2015 at 2:23 PM, Marc Abramowitz wrote:
> I agree with you. I find it a bit tedious to have to create a playbook just
> to apply a role.
>
> You might be interested in t
I agree with you. I find it a bit tedious to have to create a playbook just
to apply a role.
You might be interested in this PR, which I just submitted:
https://github.com/ansible/ansible/pull/11416
--
You received this message because you are subscribed to the Google Groups
"Ansible Project"
"Methodological issue, not practical: it feels dirty to edit a file between
the test and the application."
I wouldn't look at it this way.
To edit the role, perhaps, likely, yes.
But the idea that a playbook is simply mapping roles to hosts -- and
keeping playbooks at top level very simple -- sh
On Monday, June 2, 2014 9:58:37 PM UTC-7, john...@caradvice.com.au wrote:
>
> without having to edit any files between getting it finished...
>
>
> Methodological issue, not practical: it feels dirty to edit a file between
> the test and the application.
> Is creating and editing a new file the
john@caradvice.com.au napisał:
>
>>
>> without having to edit any files between getting it finished...
>
>
>Methodological issue, not practical: it feels dirty to edit a file
>between
>the test and the application.
>Is creating and editing a new file the only way to get from the
>"tested"
>
>
> without having to edit any files between getting it finished...
Methodological issue, not practical: it feels dirty to edit a file between
the test and the application.
Is creating and editing a new file the only way to get from the "tested"
codebase to applying it to production hosts?
O
If you're just testing that one role, why not make a simple playbook that
calls just that?
- hosts: all
roles:
- thisone
That should be all you need, since you're pointing it at different
inventory sources.
On Mon, Jun 2, 2014 at 10:06 PM, wrote:
> I want to develop/test my new role on a
I want to develop/test my new role on a virtual node thence apply just that
one play, um role, against a host that really matters.
How do I do that without having to edit any files between getting it
finished and applying it to production?
# this doesn't work...
% ansible-playbook -i testing ro
11 matches
Mail list logo
