The behavior is the same if I specify -i ec2.py. I like to specify
inventory manually instead of making it a global setting. Are you saying
the yml should call the python script?
On Thu, Dec 13, 2018 at 10:07 PM Tony Chia wrote:
>
>
> That is expected.
>
> If you don’t specify -i how the
You can probably reduce some time by setting the region that expect your
resource to be in and one or note tags in the ex2.ini file
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails
That is expected.
If you don’t specify -i how the ansible-playbook know you want to run against
production or staging or test env ?
You could probably set some defaults using the inventory setting under
defaults section in ansible.cfg. For example
Hi,
I'm working on a job template in Tower that needs to be run as root. On our
target hosts, we have it setup so you must use the command "sesu" to become
root. Currently, I'm using become_exe in the ansible.cfg file to specify
the sesu command. This works when password-less sesu is enabled.
Hi all,
Ansible 2.5.14, 2.6.11, and 2.7.5 were released today. These releases
include a fix for a reported security vulnerability, CVE-2018-16876
https://bugzilla.redhat.com/show_bug.cgi?id=1657330 as well as other
general bugfixes.
CVE-2018-16876 prevented Ansible from respecting the no_log
Every time I run this plugin, it takes at least a minute to get anything
back. Each time it is execute I can see a new cache being built inside
~/.ansible/tmp. Has anyone else had this problem?
$ time ./ec2.py --refresh-cache > /dev/null
On Thu, 13 Dec 2018 at 17:42, danish09 wrote:
>
> amazing. thanks a lot. tried it just now and it did the magic. However, tried
> to give it a little thought. I am assuming 1 is for the expression with in
> the first bracket (). But since it is an OR '|', how does it know which word
> needs to
I think that you can send the output into a file and then you can read it
,,,
*nohup*. *nohup* is a POSIX *command* to ignore the HUP (hangup) signal.
The HUP signal is, by convention, the way a terminal warns dependent
processes of logout. Output that would normally go to the terminal goes to
a
amazing. thanks a lot. tried it just now and it did the magic. However,
tried to give it a little thought. I am assuming 1 is for the expression
with in the first bracket (). But since it is an OR '|', how does it know
which word needs to be replaced with what and in which line. I mean could
Even I have issues running ansible with powerbroker.
Can you please advise?
The output from ansible server is
TRUNCATED**
ESTABLISH SSH CONNECTION FOR USER: ithakur
SSH: EXEC sshpass -d14 ssh -C -o
ControlMaster=auto -o ControlPersist=60s -o
Hi Stefano,
I'm too working with the expect module for automating bmc shell upgrade for
which I need to telnet to a machine and then login into its bmc shell
followed by some commands.
The problem I'm facing is while logging into the its bmc shell I need to
enter user and password followed by
tou ahould check out AWX
On Thu, Dec 13, 2018 at 12:19 AM pradeep.hk wrote:
> Got it. Thanks for your time.
> My requirement is to be able to sequence together tasks(to create a
> workflow) and after some prototyping, I found ansible playbook to meet that
> requirement.
> But then, scalability
This should do it:
- name: backup conf file and search and replace regex
replace:
path: /etc/nginx/sites-available/cruk-eb
regexp: '(privkey|cert)\.cruk\.org\.(key\.pem|crt)'
replace: '\g<1>3.pem'
backup: yes
Dick
On Thu, 13 Dec 2018 at 11:23, danish09
Hey there,
I am using ansible 2.6.4. In on the projects I was working on, I had to
search for 2 different words in the same file and replace them as
necessary. Used *replace* module 2 times for this. Below is the playbook
that I have used.
- name: backup conf file and search and replace
Good Day,
How would one compose a list of VM's to make changes against. I have the
following which works for a single machine :
*- hosts: 127.0.0.1 tasks: - name: Change NIC Configuration
delegate_to: localhostvmware_guest: hostname: X
username:
I found out that I was using older ansible version v2.6.2. This is fixed in
later version of ansible.
Now I've updated to latest ansible v2.7.4 version and deleting AWS user is
working.
I can delete like this:
- name: Absent iam user
iam:
iam_type: user
state: absent
16 matches
Mail list logo