saltstack/salt
1
0
Fork 0
mirror of https://github.com/saltstack/salt.git synced 2025-04-17 10:10:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Add userdata_renderer fix info to 2016.11.4 release notes

Browse source
This commit is contained in:
Erik Johnson 2017-03-31 10:25:43 -05:00
parent 111188742a
commit a85a416c72
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/topics/releases/2016.11.4.rst
View file

@ -21,3 +21,25 @@ makes cache operations faster. It doesn't make much sence for the ``localfs``
cache driver but helps for more complex drivers like ``consul``.
For more details see ``memcache_expire_seconds`` and other ``memcache_*``
options in the master config reverence.
Salt-Cloud Fixes
================
2016.11.0 added support for templating userdata files for the :mod:`ec2
<salt.cloud.clouds.ec2>` driver, using the :conf_master:`renderer` option from
the master config file. However, as the default renderer first evaluates jinja
templating, followed by loading the data as a YAML dictionary, this results in
unpredictable results when userdata files are comprised of non-YAML data (which
they generally are).
2016.11.4 fixes this by setting the default renderer used to template userdata
files to ``jinja``, and adding a new cloud profile config parameter called
``userdata_renderer``. If this option is not set, then salt-cloud will fall
back to using the new master configuration parameter
:conf_master:`userdata_renderer`.
In addition, the other cloud drivers which support setting a ``userdata_file``
(:mod:`azurearm <salt.cloud.clouds.azurearm>`, :mod:`nova
<salt.cloud.clouds.nova>`, and :mod:`openstack <salt.cloud.clouds.openstack>`)
have had templating support added to bring them to feature parity with ec2's
implementation of the ``userdata_file`` param.