vyos-cloud-init.git/templates, branch 20.4

Add Alpine Linux support. (#535)

2020-08-19T23:18:25+00:00

Add new module cc_apk_configure for creating Alpine /etc/apk/repositories file. Modify cc_ca_certs, cc_ntp, cc_power_state_change, and cc_resolv_conf for Alpine. Add Alpine template files for Chrony and Busybox NTP support. Add Alpine template file for /etc/hosts.

Add update_etc_hosts as default module on *BSD (#479)

2020-07-07T13:20:11+00:00

* Add update_etc_hosts as default module on *BSD * Set preference of IPv6 over IPv4 in FreeBSD /etc/hosts

Enable chef_license support for chef infra client (#389)

2020-05-27T22:49:38+00:00

Co-authored-by: Daniel Watkins

make suse and sles support 127.0.1.1 (#336)

2020-05-07T17:01:22+00:00

Move from 127.0.0.1 to 127.0.1.1 for localhost IP addr for opensuse and sles

cc_resolv_conf: introduce tests and stabilise output across Python versions (#251)

2020-03-13T19:49:42+00:00

This is a follow-up to #144 which fixed the rendering behaviour. While writing the tests, CI failed due to dict iteration differences across Python versions, so this also sorts output so that we will produce the same output across Python versions.

fix minor issue with resolv_conf template (#144)

2020-03-12T21:13:28+00:00

templates/ntp.conf.debian.tmpl: fix missing newline for pools

2019-07-16T20:57:32+00:00

The debian ntp.conf template did not contain a newline for the comment used to mark the rendered ntp pools configured. This resulted in an invalid line: '# poolspool 0.int.pool.ntp.org iburst' rather than: '# pools pool 0.int.pool.ntp.org iburst' This patch fixes the template and updates the unittest to verify that the rendered templates puts servers and pools at the beginning of a line. LP: #1836598

Enable encrypted_data_bag_secret support for Chef

2019-02-25T19:09:39+00:00

Encrypted data bags require a secrets file to be present to decrypt, and the location of the file must be configured the Chef client configuration file, client.rb. This update enables cloud-init's chef module to update that setting in client.rb. LP: #1817082

Ubuntu: update sources.list to comment out deb-src entries.

2018-10-04T18:20:12+00:00

Other installation modes began to comment out the deb-src lines in /etc/apt/sources.list sometime in 16.04 time frame. This makes the cloud-init rendered sources.list the same as that currently present in the lxd images. The changes here are: a.) comment out all 'deb-src' lines. b.) move security to the bottom of the file. c.) trim trailing white space from 3 comment lines. LP: #74747

renderer: support unicode in render_from_file.

2018-04-12T21:51:07+00:00

If a file passed to render_from_file had non-ascii text then jinja in python2 would decode as ascii, which would cause UnicodeDecodeError. This issue can be re-created in python2 with just: 'can\xe2\x80\x99t'.decode() The solution here is to explicitly pass in unicode supporting type (py3 str, py2 unicode). Those are six.text_type. Then jinja does not try to decode. The reason we hit this is that load_file calls decode_binary. decode_binary believes it has no work to do if it got a six.string_types. isinstance('can\xe2\x80\x99t', six.string_types) == True So it returns the original string which will blow up for jinja. Our fix here then is to load the file in binary mode and explicitly decode it to utf-8. Then in python2 we'll have a unicode type and in python3 we'll have a string type.