vyos-cloud-init.git/doc/examples/cloud-config-datasources.txt, branch circinus-public-unmaintained

sources/azure: remove unnecessary hostname bounce (#1143)

2021-12-10T17:16:16+00:00

Thanks to [1], the hostname is set prior to network bring-up. The Azure data source has been bouncing the hostname during setup(), occurring after the hostname has already been properly configured. Note that this doesn't prevent leaking the image's hostname during Azure's _get_data() when it brings up ephemeral DHCP. However, as are not guaranteed to have the hostname metadata available from a truly "local" source, this behavior is to be expected unless we disable `send host-name` from dhclient config. [1]: https://github.com/canonical/cloud-init/commit/133ad2cb327ad17b7b81319fac8f9f14577c04df Signed-off-by: Chris Patterson

sources/azure: remove unused remnants related to agent command (#1119)

2021-11-29T15:59:39+00:00

Some references were missed in the removal of the agent command in PR #799. This simply removes the remaining references. Signed-off-by: Chris Patterson

Add test to ensure docs examples are valid cloud-init configs (#355)

2020-05-08T21:38:51+00:00

Also update all examples to include the cloud-config header if they don't have it LP: #1876414

YAML align indent sizes for docs readability (#323)

2020-04-22T18:38:15+00:00

This proposal has been aligned in a human readable. There are no changes to this except for spac The indentation size is not specifically defined in the YAML RFC $ make yaml has passed on my-machine I set the indentation size to the largest number of articles in the repository (dictionary: 2) (And also include nishigori as a CLA signer.)

Fix typo in publicly viewable documentation.

2019-07-16T16:28:24+00:00

SmartOS: Add support for Joyent LX-Brand Zones (LP: #1540965)

2016-02-04T21:52:08+00:00

LX-brand zones on Joyent's SmartOS use a different metadata source (socket file) than the KVM-based SmartOS virtualization (serial port). This patch adds support for recognizing the different flavors of virtualization on SmartOS and setting up a metadata source file object. After the file object is created, the rest of the code for the datasource LP: #1540965

fix 'make yaml'.

2013-12-12T19:22:14+00:00

changes to behavior on specifying keys.

2013-08-24T04:07:35+00:00

The most likely end user operation (or at least a valid one) for base64 encoding would be to encode the user-data, but leave all other values as plaintext. In order to facilitate that, the user can simply add: b64-user-data=true to indicate that user-data is base64 encoded. Other changes here are to change the cloud-config and metadata keynames that are used. base64_all = boolean(True) base64_keys = [list, of, keys] Fixed up tests to accomodate.

Fixed no_base64_decode settings

2013-08-20T15:56:25+00:00

azure: support bouncing interfaces to publish new hostname

2013-07-25T18:37:10+00:00

See the added doc/sources/azure/README.rst for why this is necessary. Essentially, we now are doing the following in the get_data() method of azure datasource to publish this NewHostname: hostname NewHostName ifdown eth0; ifup eth0 LP: #1202758