Hi all,
We are releasing a new set of candidates for the security bug in
CVE-2016-9587:
2.1.4 RC3
2.2.1 RC5
Due to this release, we are moving the final release to Monday, January
16th. Sorry for the delay in getting the finals out.
Thanks!
James Cammarata
Ansible Lead/Sr. Principal Software
To All in the Ansible Community,
As you've likely heard, Computest.nl reported a security vulnerability to
the Ansible Core engineering team and Red Hat Security. The Ansible Core
team has been working hard to fix the issues and has released Release
Candidates to the 2.1.x branch and the
To All in the Ansible Community,
As you've likely heard, Computest.nl reported a security vulnerability to
the Ansible Core engineering team and Red Hat Security. The Ansible Core
team has been working hard to fix the issues and has released Release
Candidates to the 2.1.x branch and the
If I execute $ . ${WL_HOME}/server/bin/setWLSEnv.sh
I get 36 new and 2 modified environment variables, ideally I don't want the
consumer of my custom module to not have to specifiy these manually. I
would like the consumer to specify WL_HOME, then get the ansible module
framework to execute
