Dear all,
I have defined a var which contains some special characters (actually, a
password in a vault).
Let's assume the vault contains :
myPasswd: foo@bar
There is no problem when creating the encrypted file.
When I use it somewhere in a playbook, for example :
password: "{{ myPasswd }}"
I g
target for the playbook.
So, thanks for your help ;)
This question is closed.
Best Regards.
J-L
Le lundi 24 juin 2019 11:48:20 UTC+2, JiElPe-Fr38 a écrit :
>
> Dear all,
>
> I have a problem with the jenkins_plugins module.
> Within a playbook that pull a jenkins docker im
Dear all,
I have a problem with the jenkins_plugins module.
Within a playbook that pull a jenkins docker image
(jenkins/jenkins:lts-alpine) and runs it to install the instance and
configure it, I have a task that install a list of plugins on an instance,
which is :
- name: Install plugins
j
ue on Github.
> #24864
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fansible%2Fansible%2Fissues%2F24864&sa=D&sntz=1&usg=AFQjCNGO8ycAoswwat7sZlQPyoBVfGr-vQ>
>
> On Tuesday, April 3, 2018 at 5:43:45 PM UTC+5:30, JiElPe-Fr38 wrote:
>>
>> Dea
Dear all,
I have created a jenkins role that creates a jenkins instance and add
plugins.
The task related to plugins is as follows :
- name: Install plugins
jenkins_plugin:
group: "{{ jenkins_process_group }}"
owner: "{{ jenkins_process_user }}"
name: "{{ item }}"
state: latest
Dear all,
I am really stucked with this problem.
I have a vault file which is referenced within ansible.cfg and its password
is stored in a file referenced on the command line through
--vault-password-file.
This seems to be ok.
My vault contains (silly example for trials):
jenkins: totototo
I
Thanks for the idea...
In fact, I already used the verbose mode, so yes I can confirm that it uses
the awaited config file.
Which is not a good news, because it would have been a good reason for the
problem.
J-L
Le jeudi 8 mars 2018 11:49:16 UTC+1, JiElPe-Fr38 a écrit :
>
> Dear all,
&g
Dear all,
I am "auto learning" ansible and currently try to understand how to use
vault.
To summarize things, I have created a vault.yml file in the vars directory,
and included it in the main.yml task. Then, I put the vault password within
a .vault_passwd file created at the same level than an
_family }} host"
when: ansible_pkg_mgr == 'yum'
become: true
become_user: root
As mentioned in the answers, notify must not be set at block level, but
after each enclosed task.
Thanks for your help.
Have a nice day.
JiElPe
Le mercredi 31 janvier 2018 16:29:00 UTC+1, JiE
Dear all,
I am quite new to Ansible and try to "make a tour"...
I am using ansible 2.4.2.0 with cygwin64 on Win7.
I am currently make a personal training and find that I could use a block
to "enclose" (ok, perhaps wrong term) a couple of task that have some
common "properties" (like become_use
10 matches
Mail list logo