(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.1 2020-02-20T20:55:21+00:00 2020-02-20T20:55:21+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-02-20T20:55:21+00:00 urn:sha1:13e82554728b1cb524438163784e5b955c7c5ed0 Bump the version in cloudinit/version.py to 20.1 and update ChangeLog. LP: #1863954 2020-02-20T17:11:04+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-02-20T17:11:04+00:00 urn:sha1:4ad5c5d058cc9501ef2f294cb6430d9ffe372e7d * tools/read-version: don't enforce version parity in release branch CI We have a bootstrapping problem with new releases, currently. To take the example of 20.1: the branch that bumps the version fails CI because there is no 20.1 tag for it to use in read-version. Previously, this was solved by creating a tag and pushing it to the cloud-init repo before the commit landed. However, we have GitHub branch protection enabled, so the commit that needs to be tagged is not created until the pull request lands in master. This works around this problem by introducing a very specific check: if we are performing CI for an upstream release branch, we skip the read-version checking that we know will fail. * tools/make-tarball: add --version parameter When using make-tarball as part of a CI build of a new upstream release, the version it determines is inconsistent with the version that other tools determine. Instead of encoding the logic here (as well as in Python elsewhere), we add a parameter to allow us to set it from outside the script. * packages/bddeb: handle missing version_long in new version CI If we're running in CI for a new upstream release, we have to use `version` instead of `version_long` (because we don't yet have the tag required to generate `version_long`). 2020-02-19T21:01:09+00:00 Ryan Harper ryan.harper@canonical.com 2020-02-19T21:01:09+00:00 urn:sha1:87cd040ed8fe7195cbb357ed3bbf53cd2a81436c Instead of logging the token values used log the headers and replace the actual values with the string 'REDACTED'. This allows users to examine cloud-init.log and see that the IMDSv2 token header is being used but avoids leaving the value used in the log file itself. LP: #1863943 2020-02-18T17:03:24+00:00 Dimitri John Ledkov xnox@ubuntu.com 2020-02-18T17:03:24+00:00 urn:sha1:3e2f7356effc9e9cccc5ae945846279804eedc46 As noticed by Seth Arnold, non-deterministic SystemRandom should be used when creating security sensitive random strings. 2020-02-14T02:48:34+00:00 Chad Smith chad.smith@canonical.com 2020-02-14T02:48:34+00:00 urn:sha1:c90932f5cb68e789636c5e6b0b74fceb1d38c6a4 2020-02-13T20:11:17+00:00 Ryan Harper ryan.harper@canonical.com 2020-02-13T20:11:17+00:00 urn:sha1:ecffd25df840277ab1fa7d5372659abe833cacbe The azurecloud platform did not always start instances during collect runs. This was a result of two issues. First the image class _instance method did not invoke the start() method which then allowed collect stage to attempt to run scripts without an endpoint. Second, azurecloud used the image_id as both an instance handle (which is typically vmName in azure api) as well as an image handle (for image capture). Resolve this by adding a .vm_name property to the AzureCloudInstance and reference this property in AzureCloudImage. Also in this branch - Fix error encoding user-data when value is None - Add additional logging in AzureCloud platform - Update logging format to print pathname,funcName and line number This greatly eases debugging. LP: #1861921 2020-02-10T16:17:56+00:00 Ryan Harper ryan.harper@canonical.com 2020-02-10T16:17:56+00:00 urn:sha1:81c7477a55b509a33af38bc502b1e9dd4ea643ff 2020-02-07T22:52:06+00:00 Ryan Harper ryan.harper@canonical.com 2020-02-07T22:52:06+00:00 urn:sha1:890aca4777ab61e54b6b96d251c3022cbe0b108c 2020-02-07T22:03:17+00:00 Igor Galić me+git@igalic.co 2020-02-07T22:03:17+00:00 urn:sha1:616d0a60d8d6ef0fa024267e718b3ed0e3b6bbdc bugzilla ref: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224361 svn rev: https://svnweb.freebsd.org/ports?view=revision&revision=457768 2020-02-07T21:24:31+00:00 Edwin Kofler 24364012+eankeen@users.noreply.github.com 2020-02-07T21:24:31+00:00 urn:sha1:b285efb97947af1966b2a46df30e0764ba44aa55 fixes typo at doc/examples/cloud-config-disk-setup.txt; Cavaut => Caveat