Hi Vlado,
That does make more sense. Thank you.
On Wednesday, 23 October 2019 10:32:17 UTC+1, Vladimir Botka wrote:
>
> Hi Stephen,
>
> On Wed, 23 Oct 2019 01:51:26 -0700 (PDT)
> Stephen Feyrer > wrote:
>
> > - name: my-script
> > sc
s
Stephen.
On Wednesday, 23 October 2019 09:19:46 UTC+1, Vladimir Botka wrote:
>
> On Mon, 21 Oct 2019 09:34:22 -0700 (PDT)
> Stephen Feyrer > wrote:
>
> > vault_password: abc(123
> > ---
> > tasks:
> > - name: my-script
> >script: My-Script.ps1
{{ vault_password | quote }}
and
- name: my-script
script: My-Script.ps1 -secret {{ vault_password | join("") }}
Both produced the same result as before.
Thank you.
On Monday, 21 October 2019 18:51:46 UTC+1, Vladimir Botka wrote:
>
> On Mon, 21 Oct 2019 09:34:22 -0700 (PDT)
> Ste
Hi there,
I have a password vault and a script to which I am passing a password.
The vault looks kind of like this:
---
vault_password: abc(123
The script in the playbook is called like this:
---
tasks:
- name: my-script
script: My-Script.ps1 -secret {{ vault_password }}
The error which
ommand oriented), then you are
> definitely going with the grain of how ansible is supposed to work and you
> will gain the benefit of more easily readable playbooks.
>
> Hope this helps,
>
> Jon
>
> On Friday, October 4, 2019 at 11:58:05 AM UTC+1, Stephen Feyrer wr
Hi,
On Friday, 4 October 2019 11:46:27 UTC+1, Stephen Feyrer wrote:
>
> Hi everyone,
>
> The goal is to make the host reboot only if the ansible-fact
> 'reboot_pending' is true. This is achieved but generates a warning, is
> there a better way of doing this?
>
>
J
Hi everyone,
I apologise, I am new to Ansible and this is rather open ended.
After extensive use of the documentation I have my inventory, vars, vault
and playbook all working together. However, there is room for improvement.
This is my simple proof of concept playbook:
---
- name: Run
