(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 2022-01-10T22:56:29+00:00 2022-01-10T22:56:29+00:00 James Falcon james.falcon@canonical.com 2022-01-10T22:56:29+00:00 urn:sha1:dc1aabfca851e520693c05322f724bd102c76364 Includes: - Update tox.ini and .travis.yml accordingly - Cleanup tox.ini with new tox syntax and cloud-init dependencies - Update documentation accordingly - Replace/remove xenial references where additional testing isn't required - Remove xenial checks in integration tests - Replace yield_fixture with fixture in pytest tests Sections of code commented with lines like "Remove when Xenial is no longer supported" still exist as they're require additional testing. 2021-11-01T18:42:59+00:00 Brett Holman bholman.devel@gmail.com 2021-11-01T18:42:59+00:00 urn:sha1:b1beb53886527eb787b504f374f24a7bd5fe06ac Don't throw an exception when mirror arch is unspecified. 2021-10-29T19:33:33+00:00 Brett Holman brett.holman@canonical.com 2021-10-29T19:33:33+00:00 urn:sha1:28581988da4b37e3d2423075c64dc1f3bc5da5cc Also, add the "signed by" option to source definitions. This enables users to limit the scope of trust for individual keys. LP: #1836336 2021-05-18T17:02:51+00:00 Paul Goins paul.goins@canonical.com 2021-05-18T17:02:51+00:00 urn:sha1:1793b8b70ca2e3587c271155033ef943207136ae Presently, mirror keys cannot be associated with primary/security mirrors. Unfortunately, this prevents use of Landscape-managed package mirrors as the mirror key for the Landscape-hosted repository cannot be provided. This patch allows the same key-related fields usable on "sources" entries to be used on the "primary" and "security" entries as well. LP: #1925395 2020-05-13T20:45:01+00:00 lucasmoura lucas.moura@canonical.com 2020-05-13T20:45:01+00:00 urn:sha1:2e32c40a607250bc9e713c0daf360dc6617f4420 Create a schema object for the `apt_configure` module and validate this schema in the `handle` function of the module. There are some considerations regarding this PR: * The `primary` and `security` keys have the exact same properties. I tried to eliminate this redundancy by moving their properties to a common place and then just referencing it for both security and primary. Similar to what is documented here: https://json-schema.org/understanding-json-schema/structuring.html under the `Reuse` paragraph. However, this approach does not work, because the `#` pointer goes to the beginning of the file, which is a python module instead of a json file, not allowing the pointer to find the correct definition. What I did was to create a separate dict for the mirror config and reuse it for primary and security, but maybe there are better approaches to do that. * There was no documentation for the config `debconf_selections`. I tried to infer what it supposed to do by looking at the code and the `debconf-set-selections` manpage, but my description may not be accurate or complete. * Add a _parse_description function to schema.py to render multi-line preformatted content instead of squashing all whitespace LP: #1858884 2020-05-08T21:38:51+00:00 James Falcon TheRealFalcon@users.noreply.github.com 2020-05-08T21:38:51+00:00 urn:sha1:34b868020254106af8c79ffb85e04e294b19e44f Also update all examples to include the cloud-config header if they don't have it LP: #1876414 2020-04-22T18:38:15+00:00 Tak Nishigori nishigori.tak@gmail.com 2020-04-22T18:38:15+00:00 urn:sha1:1b049e6e51a9ac1ca02bf33629ede5c47c5b1941 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.) 2016-12-03T01:20:41+00:00 Scott Moser smoser@brickies.net 2016-12-03T01:20:41+00:00 urn:sha1:166df605dc9864eb163007300db7a611feb309d6 Python 3 would fail to load yaml from doc/examples/cloud-config-apt.txt when the LANG (specifically LC_CTYPE) was 'C'. The changes here do 2 things: a.) remove the non-ascii characters from the yaml file. b.) fix the validate-yaml.py program to decode using utf-8 specifically rather than using the inherited settings. This fixes it now for ascii and in the future also should non-ascii slip in. 2016-08-18T15:02:44+00:00 Christian Ehrhardt christian.ehrhardt@canonical.com 2016-08-10T14:43:14+00:00 urn:sha1:d861415ff9ab816b1183b8c58ec35348be4fd458 This adds an improved apt configuration format that is fully backwards compatible with previous behavior. This is mostly copied from curtin's implementation. It does: * clean up and centralizes many of the top level 'apt_*' values that previously existed into a single top level 'apt'key. * support a 'source' in apt/sources/entry that has only a key * documents new features and adds tests. See the added doc/examples/cloud-config-apt.txt for more information.