mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
Documentation updates
This commit is contained in:
parent
582f088e7e
commit
908a192736
1 changed files with 25 additions and 26 deletions
|
@ -580,32 +580,41 @@ It is quite possible that you may need to get package updates through a proxy, o
|
||||||
updates through a proxy and access other packages not through a proxy. Ansible makes it easy for you
|
updates through a proxy and access other packages not through a proxy. Ansible makes it easy for you
|
||||||
to configure your environment by using the 'environment' keyword. Here is an example::
|
to configure your environment by using the 'environment' keyword. Here is an example::
|
||||||
|
|
||||||
- hosts: all
|
- hosts: all
|
||||||
user: root
|
user: root
|
||||||
|
|
||||||
tasks:
|
tasks:
|
||||||
|
|
||||||
- apt: name=cobbler state=installed
|
- apt: name=cobbler state=installed
|
||||||
environment:
|
environment:
|
||||||
http_proxy: http://proxy.example.com:8080
|
http_proxy: http://proxy.example.com:8080
|
||||||
|
|
||||||
The environment can also be stored in a variable, and accessed like so::
|
The environment can also be stored in a variable, and accessed like so::
|
||||||
|
|
||||||
- hosts: all
|
- hosts: all
|
||||||
user: root
|
user: root
|
||||||
|
|
||||||
# here we make a variable named "env" that is a dictionary
|
# here we make a variable named "env" that is a dictionary
|
||||||
vars:
|
vars:
|
||||||
env:
|
proxy_env:
|
||||||
http_proxy=http://proxy.example.com:8080
|
http_proxy=http://proxy.example.com:8080
|
||||||
|
|
||||||
tasks:
|
tasks:
|
||||||
|
|
||||||
- apt: name=cobbler state=installed
|
- apt: name=cobbler state=installed
|
||||||
environment: $env
|
environment: $proxy_env
|
||||||
|
|
||||||
While just proxy settings were shown above, any number of settings can be supplied.
|
While just proxy settings were shown above, any number of settings can be supplied. The most logical place
|
||||||
|
to define an environment hash might be a group_vars file, like so::
|
||||||
|
|
||||||
|
----
|
||||||
|
# file: group_vars/boston
|
||||||
|
|
||||||
|
ntp_server: ntp.bos.example.com
|
||||||
|
backup: bak.bos.example.com
|
||||||
|
proxy_env:
|
||||||
|
http_proxy=http://proxy.bos.example.com:8080
|
||||||
|
https_proxy=http://proxy.bos.example.com:8080
|
||||||
|
|
||||||
Getting values from files
|
Getting values from files
|
||||||
`````````````````````````
|
`````````````````````````
|
||||||
|
@ -630,16 +639,6 @@ Because Ansible uses lazy evaluation, a "$PIPE" macro will be executed each time
|
||||||
example, it will be executed separately for each host, and if it is used in a variable definition,
|
example, it will be executed separately for each host, and if it is used in a variable definition,
|
||||||
it will be executed each time the variable is evaluated.
|
it will be executed each time the variable is evaluated.
|
||||||
|
|
||||||
.. versionadded:: 1.1
|
|
||||||
|
|
||||||
The "$PIPE_ONCE" macro is an alternative that uses a caching strategy: it is executed only once, and
|
|
||||||
subsequent accesses use the cached value. One use case is for computing a timestamp that is intended
|
|
||||||
to be the same across all tasks and hosts that use it::
|
|
||||||
|
|
||||||
vars:
|
|
||||||
timestamp: $PIPE_ONCE(date +%Y%m%d-%H%M%S)
|
|
||||||
|
|
||||||
|
|
||||||
Selecting Files And Templates Based On Variables
|
Selecting Files And Templates Based On Variables
|
||||||
````````````````````````````````````````````````
|
````````````````````````````````````````````````
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue