Version 2016.11.4 is a bugfix release for 2016.11.0.
AIX support has been added for the following execution modules:
Memcache is now supported as a data store for the minion data cache.
Memcache is an additional cache layer that keeps a limited amount of data
fetched from the minion data cache for a limited period of time in memory that
makes cache operations faster. It doesn't make much sense for the
cache driver but helps for more complex drivers like
For more details see
memcache_expire_seconds and other
options in the master config reverence.
dockerng.loginhas been added, which authenticates to the registry and adds the credential token to the
~/.docker/config.json. After upgrading, if you have not already performed a
docker loginon the minion using the docker CLI, you will need to run
dockerng.loginto login. This only needs to be done once.
myregistry.com:5000/image:tagname) has been fixed. In previous releases, Salt would use the colon to separate the tag name from the image name, and if there was no colon, the default tag name of
latestwould be assumed. However, this caused custom registry images to be misidentified when no explicit tag name was passed (e.g.
myregistry.com:5000/image). To work around this in earlier releases, simply specify the tag name.
2016.11.0 added support for templating userdata files for the
ec2 driver, using the
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 only templating the userdata_file when it is explicitly
configured to do so. This is done by adding a new optional parameter to the
cloud profile called
userdata_template. This option is used in the same way
template argument in
file.managed states, it is simply set to the desired templating
my-ec2-config: # Pass userdata to the instance to be created userdata_file: /etc/salt/my-userdata-file userdata_template: jinja
userdata_template option is set in the cloud profile, then
salt-cloud will check for the presence of the master configuration parameter
userdata_renderer. If this is also not set, then no templating
will be performed on the userdata_file.
In addition, the other cloud drivers which support setting a
have had templating support added to bring them to feature parity with the ec2
driver's implementation of the
Generated at: 2018-05-27 19:46:47 UTC