<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/distros, branch crux</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2021-02-13T17:49:57+00:00</updated>
<entry>
<title>Update debian eni network configuration location, retain Ubuntu setting</title>
<updated>2021-02-13T17:49:57+00:00</updated>
<author>
<name>Janos Lenart</name>
<email>ocsi@debian.org</email>
</author>
<published>2019-07-15T21:26:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=377d1bbbdd45aad25c36ab15ce15c93a39df4ce9'/>
<id>urn:sha1:377d1bbbdd45aad25c36ab15ce15c93a39df4ce9</id>
<content type='text'>
On Debian, ifupdown uses `source-directory /etc/network/interfaces.d`
(for new installs) to include files.
https://salsa.debian.org/debian/ifupdown/blob/master/debian/postinst#L23

The current filename, 50-cloud-init.cfg, does not match against the RE
that is used to scan the directory for configurations (ASCII upper- and
lower-case letters, ASCII digits, ASCII underscores, and ASCII
minus-hyphens):
https://salsa.debian.org/debian/ifupdown/blob/master/interfaces.5.pre#L122

Of course many installations use `source /etc/network/interfaces.d/*`,
but not all.
</content>
</entry>
<entry>
<title>pylint: ignore warning assignment-from-no-return for _write_network</title>
<updated>2018-09-21T08:39:17+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-09-21T08:39:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1c63a4f5d5cc045ef66291afe1694bd58cc059af'/>
<id>urn:sha1:1c63a4f5d5cc045ef66291afe1694bd58cc059af</id>
<content type='text'>
Distro subclasses arch, freebsd and debian still have a path with an
implemented _write_network method which has a return value. Can drop
this pylint ignore when _write_network is dropped from arch, freebsd
and debian.
</content>
</entry>
<entry>
<title>Remove dead-code _write_network distro implementations.</title>
<updated>2018-09-20T09:08:37+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-09-20T09:08:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c3680475f9c97028d75a8f1bb58139ddd47d00ed'/>
<id>urn:sha1:c3680475f9c97028d75a8f1bb58139ddd47d00ed</id>
<content type='text'>
Any distro that has a '_write_nework_config' method should no
longer get their _write_network called at all.  So lets drop
that code and raise a RuntimeError any time we got there.

Replace the one caller of 'apply_network' (legacy openstack path)
with a call to apply_network_config after converting the ENI to
network config.
</content>
</entry>
<entry>
<title>net_util: ensure static configs have netmask in translate_network result</title>
<updated>2018-09-18T07:16:40+00:00</updated>
<author>
<name>Thomas Berger</name>
<email>loki@lokis-chaos.de</email>
</author>
<published>2018-09-18T07:16:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=98d18c31c8759add858096dea53bc093c7cc9caa'/>
<id>urn:sha1:98d18c31c8759add858096dea53bc093c7cc9caa</id>
<content type='text'>
If a DataSource provides a network configuration in version 2 and runs
on a distro which does not have a network renderer class in use, then
the conversion of V2 to eni results in static ip configurations with
subnet prefix-length (192.168.23.1/24) rather than explicit netmask
value.

When sending such a config to net_util.translate_network the resulting
dictionary is missing the 'netmask' key for static configured addresses
breaking network configurations on multiple distributions.

This patch detects static ip configurations using prefix-length and
converts the format into the previous 'address' and 'netmask' parts
to keep compatibility for these distribtuions until they move to
the v2 network configuration.

LP: #1792454
</content>
</entry>
<entry>
<title>config: disable ssh access to a configured user account</title>
<updated>2018-09-08T01:48:38+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-09-08T01:48:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=757247f9ff2df57e792e29d8656ac415364e914d'/>
<id>urn:sha1:757247f9ff2df57e792e29d8656ac415364e914d</id>
<content type='text'>
Cloud config can now disable ssh access to non-root users.

When defining the 'users' list in cloud-configuration a boolean
'ssh_redirect_user: true' can be provided to disable ssh logins for
that user. Any ssh 'public-keys' defined in cloud meta-data will be added
and disabled in .ssh/authorized_keys. Any attempts to ssh as this user
using acceptable ssh keys will be presented with a message like the
following:

Please login as the user "ubuntu" rather than the user "youruser".
</content>
</entry>
<entry>
<title>sysconfig: refactor sysconfig to accept distro specific templates paths</title>
<updated>2018-09-05T14:17:16+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2018-09-05T14:17:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=db50bc0d999e3a90136864a774f85e4e15b144e8'/>
<id>urn:sha1:db50bc0d999e3a90136864a774f85e4e15b144e8</id>
<content type='text'>
Multiple distros use sysconfig format but have different content
and paths to certain files.  Update distros to specify these
template paths in their renderer_configs dictionary.
</content>
</entry>
<entry>
<title>logging: Add logging config type hyperv for reporting via Azure KVP</title>
<updated>2018-08-24T22:25:37+00:00</updated>
<author>
<name>Andy Liu</name>
<email>andyliuliming@outlook.com</email>
</author>
<published>2018-08-24T22:25:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=2320c3de2712c2f320b0d8af4aa129219cc2ad04'/>
<id>urn:sha1:2320c3de2712c2f320b0d8af4aa129219cc2ad04</id>
<content type='text'>
Linux guests can provide information to Hyper-V hosts via KVP.
KVP allows the guests to provide any string key-value-pairs back to the
host's registry. On linux, kvp communication pools are presented as pool
files in /var/lib/hyperv/.kvp_pool_#.

The following reporting configuration can enable this kvp reporting in
addition to default logging if the pool files exist:

reporting:
    logging:
        type: log
    telemetry:
        type: hyperv
</content>
</entry>
<entry>
<title>Explicitly prevent `sudo` access for user module</title>
<updated>2018-06-19T22:04:17+00:00</updated>
<author>
<name>Jacob Bednarz</name>
<email>jacob.bednarz@gmail.com</email>
</author>
<published>2018-06-19T22:04:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=4d69fb44a5607e16843537be26758893f2dd79be'/>
<id>urn:sha1:4d69fb44a5607e16843537be26758893f2dd79be</id>
<content type='text'>
To deny a user elevated access, you can omit the `sudo` key from the
`users` dictionary. This works fine however it's implicitly defined
based on defaults of `cloud-init`. If the project moves to have `sudo`
access allowed for all by default (quite unlikely but still possible)
this will catch a few people out.

This introduces the ability to define an explicit `sudo: False` in the
`users` dictionary and it will prevent `sudo` access. The behaviour is
identical to omitting the key.

LP: #1771468
</content>
</entry>
<entry>
<title>pylint: pay attention to unused variable warnings.</title>
<updated>2018-04-20T03:30:08+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-04-20T03:30:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1081962eacf2814fea6f4fa3255c530de14e4a24'/>
<id>urn:sha1:1081962eacf2814fea6f4fa3255c530de14e4a24</id>
<content type='text'>
This enables warnings produced by pylint for unused variables (W0612),
and fixes the existing errors.
</content>
</entry>
<entry>
<title>pycodestyle: Fix invalid escape sequences in string literals.</title>
<updated>2018-04-18T09:35:41+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-04-18T09:35:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=acca826adf39ddfedde78cfbfc47e81a06c6f42a'/>
<id>urn:sha1:acca826adf39ddfedde78cfbfc47e81a06c6f42a</id>
<content type='text'>
Python has deprecated these invalid string literals now
  https://bugs.python.org/issue27364
and pycodestyle is identifying them with a W605 warning.
  https://github.com/PyCQA/pycodestyle/pull/676

So basically, any use of \ not followed by one of [\'"abfnrtv]
or \ooo (octal) \xhh (hex) or a newline is invalid.  This is most
comomnly seen for us in regex.  To solve, you either:
 a.) use a raw string r'...'
 b.) correctly escape the \ that was not intended to be interpreted.
</content>
</entry>
</feed>
