Hello,
I've found that I need to become administrator for some chocolatey package
installations, even when my domain user is member of local administrators
group.
To do so, I run:
tasks:
# - win_ping:
- name: become test
win_shell: whoami
become: true
become_user: administrator
This is working as designed, the runas become method is used to run a process
under a different logon type rather than escalating privileges. There is no
need to escalate privileges within WinRM as each process is run like it would
when right clicking on an exe and saying run as administrator.
Hi there,
I've setup Ansible Tower and imported a ansible project from a Git
repository.
Credentials for localhost and vault (prompt) have been added.
The playbook normally runs like this:
ansible-playbook Playbooks/vsphere-vm-provisioning/deploy-tmc.yml --ask-
vault-pas
The output in Tower
@shaikh, the command looks right, can you print both the command and
the output you get with -vvv added?
--
--
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
Hi - I want to create 3 variables based on hostname. These variables will
be used inside other tasks.
Host Pattern: mabos
Ex: mabosqa1was01
what is the best way to create variables and use for subsequent task on
host ?
should I write 3 different shell scripts to register appropriate variable
Ok, but I consider this as a workaround and not a solution (cf. comment I
wrote above).
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsub
On Fri, Dec 29, 2017 at 11:52 PM, Dhaval Joshi wrote:
> Hello
>
> I am migrating from puppet to ansible and using tower,
>
> I have question on managing data as per the role of server (dmz/core) or as
> per different region or datacentre (similar to hiradata in puppet) whats best
> way to acheiv
Hey guys!
I'd like to emulate "migration" system for ansible provisioning of my
servers. For example, let's say:
1. I add to my product "Feature A" which requires changes on hosts with
role: elasticsearch, postgres, redis
2.Then I add "feature b" which partially rollbacks changes made for featur
Ideally, I'd like to have some "incremental" strategy which stores
successfully applied "server migration" to database and then while next run
it won't execute it again
середа, 3 січня 2018 р. 01:54:53 UTC+1 користувач Sergey Glazyrin написав:
>
> Hey guys!
> I'd like to emulate "migration" sys
