The environment: directive exists so each module does not need to implement
what you are asking.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it,
Most older versions should be vulnerable, we recommend upgrading to 2.1 or
2.2 once we release the fix.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from
For hacking on new modules that will import libraries that are also being
hacked on, there doesn't appear to be a way currently to import.
Digging around recently, I saw mentions that with the ziploader addition
(which became ansiballs... great name!) that a private module_utils would
be
Does this apply to ansible 1.9?
On Monday, January 9, 2017 at 10:57:09 AM UTC-6, James Cammarata wrote:
>
> Hi all,
>
> Today we are releasing two new release candidates to address CVE-2016-9587,
> which we are removing from embargo today:
>
> 2.1.4 RC1
> 2.2.1 RC3
>
> CVE-2016-9587 is rated as
I'm working on a custom module but having issues with the environment setup
on the remote server.
How should the remote environment variables be correctly setup. I've been
looking here
http://docs.ansible.com/ansible/dev_guide/developing_modules.html but not
found anything yet or I might have
Are you will add in debian repository the fixes ?
Thank for your support
Le lundi 9 janvier 2017 17:57:09 UTC+1, James Cammarata a écrit :
>
> Hi all,
>
> Today we are releasing two new release candidates to address CVE-2016-9587,
> which we are removing from embargo today:
>
> 2.1.4 RC1
> 2.2.1
