vyos-cloud-init.git - (mirror of https://github.com/marekm72/vyos-cloud-init.git)

Age	Commit message (Collapse)	Author
2021-06-10	doc: Update NoCloud docs stating required files (#918)	James Falcon
	LP: #1931577
2021-02-25	doc: remove duplicate "it" from nocloud.rst (#825)	V.I. Wood

2020-07-02	Add mention of vendor-data to no-cloud format documentation (#470)	Landon Kirk
	Also add landon912 to .github-cla-signers
2020-04-28	DataSourceNoCloud/OVF: drop claim to support FTP (#333)	Daniel Watkins
	I don't believe this has ever been supported, looking at the git history, but it certainly isn't at the moment. LP: #1875470
2020-04-22	YAML align indent sizes for docs readability (#323)	Tak Nishigori
	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.)
2019-09-04	docs: fix whitespace, spelling, and line length	Joshua Powers

2019-04-09	Change DataSourceNoCloud to ignore file system label's case.	Risto Oikarinen
	NoCloud data source now accepts both 'cidata' and 'CIDATA' as filesystem labels. This is similar to DataSourceConfigDrive's support for 'config-2' and 'CONFIG-2'.
2017-07-11	doc: document the cmdline options to NoCloud	Brian Candler
	Add permitted keys to documentation on seeding NoCloud.
2017-06-06	NoCloud: support seed of nocloud from smbios information	Vladimir Pouzanov
	This allows the user to seed NoCloud in a trivial way from qemu/libvirt, by using a stock image and passing a single command line flag. No custom command line, no filesystem modification, no bootstrap disk image. This is particularly handy now that Ec2 backend is discouraged from use under bug 1660385. LP: #1691772
2017-05-03	doc: document network configuration defaults policy and formats.	Ryan Harper
	Add documentation for cloud-init networking configuration formats, default behavior, policy and other specific details about how network config is consumed and utilized.
2016-11-10	doc: make the RST files consistently formated and other improvements.	Scott Moser
	The biggest things here are: * move doc/sources//README.rst to doc/rtd/topics/datasources This gives each datasource a page in the rtd docs, which make it easier to read. consistently use the same header style throughout. As suggested at http://thomas-cokelaer.info/tutorials/sphinx/rest_syntax.html use: # with overline, for parts * with overline, for chapters =, for sections -, for subsections ^, for subsubsections “, for paragraphs Also, move and re-format vendor-data documentation to rtd.