<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/distros/debian.py, branch rolling</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=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2022-01-12T14:37:32+00:00</updated>
<entry>
<title>Add new config module to set keyboard layout (#1176)</title>
<updated>2022-01-12T14:37:32+00:00</updated>
<author>
<name>maxnet</name>
<email>bos@je-eigen-domein.nl</email>
</author>
<published>2022-01-12T14:37:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=5147e8d4764e368ab8ccea7433b02e4ff9d6c901'/>
<id>urn:sha1:5147e8d4764e368ab8ccea7433b02e4ff9d6c901</id>
<content type='text'>
Adds a new module to allow setting keyboard layout,
for use-cases in which cloud-init is used to configure
OS images meant for physical computers instead
of the cloud.

This initial release only implements support
for Linux distributions that allow layout to be
set through systemd's localectl.

LP: #1951593</content>
</entry>
<entry>
<title>Remove 3.5 and xenial support (SC-711) (#1167)</title>
<updated>2022-01-10T22:56:29+00:00</updated>
<author>
<name>James Falcon</name>
<email>james.falcon@canonical.com</email>
</author>
<published>2022-01-10T22:56:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=dc1aabfca851e520693c05322f724bd102c76364'/>
<id>urn:sha1:dc1aabfca851e520693c05322f724bd102c76364</id>
<content type='text'>
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.</content>
</entry>
<entry>
<title>Adopt Black and isort (SC-700) (#1157)</title>
<updated>2021-12-16T02:16:38+00:00</updated>
<author>
<name>James Falcon</name>
<email>james.falcon@canonical.com</email>
</author>
<published>2021-12-16T02:16:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf'/>
<id>urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf</id>
<content type='text'>
Applied Black and isort, fixed any linting issues, updated tox.ini
and CI.
</content>
</entry>
<entry>
<title>Include dpkg frontend lock in APT_LOCK_FILES (#1153)</title>
<updated>2021-12-15T03:26:20+00:00</updated>
<author>
<name>James Falcon</name>
<email>james.falcon@canonical.com</email>
</author>
<published>2021-12-15T03:26:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=2bcf4fa972fde686c2e3141c58e640640b44dd00'/>
<id>urn:sha1:2bcf4fa972fde686c2e3141c58e640640b44dd00</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Wait for apt lock (#1034)</title>
<updated>2021-11-09T15:28:19+00:00</updated>
<author>
<name>James Falcon</name>
<email>james.falcon@canonical.com</email>
</author>
<published>2021-11-09T15:28:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=3d150688617e2b8a16d715c7fb819c759f91915a'/>
<id>urn:sha1:3d150688617e2b8a16d715c7fb819c759f91915a</id>
<content type='text'>
Currently any attempt to run an apt command while another process holds
an apt lock will fail. We should instead wait to acquire the apt lock.

LP: #1944611</content>
</entry>
<entry>
<title>Update pylint to v2.9.3 and fix the new issues it spots (#946)</title>
<updated>2021-07-20T14:58:21+00:00</updated>
<author>
<name>Paride Legovini</name>
<email>paride.legovini@canonical.com</email>
</author>
<published>2021-07-20T14:58:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ec6afadbf0f0f77d5b58dccd70df77da89c2c91d'/>
<id>urn:sha1:ec6afadbf0f0f77d5b58dccd70df77da89c2c91d</id>
<content type='text'>
In CI run against pylint 2.9.3 and fix occurrences of:
 - W0237 (arguments-renamed)
 - W0402 (deprecated-module)

The W0402 deprecated-module was about module `imp`:

    cloudinit/patcher.py:9: [W0402(deprecated-module), ]
        Uses of a deprecated module 'imp'

The imp module is deprecated and replaced by importlib, which according
to the documentation has no replacement for acquire_lock() and
release_lock(), which are the only reason why `imp` is imported.
    
Nothing about the code using this lock that actually requires it.
Let's remove the locking code and the import altogether.

Dropping the locking makes patcher.patch() an empty wrapper around
_patch_logging(). Rename _patch_logging() to patch_logging() and
call it directly instead. Drop patch().</content>
</entry>
<entry>
<title>Add new network activators to bring up interfaces (#919)</title>
<updated>2021-07-01T19:43:07+00:00</updated>
<author>
<name>James Falcon</name>
<email>therealfalcon@gmail.com</email>
</author>
<published>2021-07-01T19:43:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=81299de5fe3b6e491a965a6ebef66c6b8bf2c037'/>
<id>urn:sha1:81299de5fe3b6e491a965a6ebef66c6b8bf2c037</id>
<content type='text'>
Currently _bring_up_interfaces() is a no-op for any distro using
renderers. We need to be able to support bringing up a single
interfaces, a list of interfaces, and all interfaces. This should be
independent of the renderers, as the network config is often
generated independent of the mechanism used to apply it.

Additionally, I included a refactor to remove
"_supported_write_network_config". We had a confusing call chain of
apply_network_config-&gt;_write_network_config-&gt;_supported_write_network_config.
The last two have been combined.</content>
</entry>
<entry>
<title>Move subp into its own module. (#416)</title>
<updated>2020-06-08T16:49:12+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2020-06-08T16:49:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=3c551f6ebc12f7729a2755c89b19b9000e27cc88'/>
<id>urn:sha1:3c551f6ebc12f7729a2755c89b19b9000e27cc88</id>
<content type='text'>
This was painful, but it finishes a TODO from cloudinit/subp.py.

It moves the following from util to subp:
  ProcessExecutionError
  subp
  which
  target_path

I moved subp_blob_in_tempfile into cc_chef, which is its only caller.
That saved us from having to deal with it using write_file
and temp_utils from subp (which does not import any cloudinit things now).

It is arguable that 'target_path' could be moved to a 'path_utils' or
something, but in order to use it from subp and also from utils,
we had to get it out of utils.</content>
</entry>
<entry>
<title>util: rename get_architecture to get_dpkg_architecture (#173)</title>
<updated>2020-01-16T18:30:12+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-01-16T18:30:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=651e24066ba4b9464c7843553f60d17a459cf06e'/>
<id>urn:sha1:651e24066ba4b9464c7843553f60d17a459cf06e</id>
<content type='text'>
This makes it clearer that we should only use this in code paths that
will definitely have dpkg available to them.

- Rename get_architecture -&gt; get_dpkg_architecture
- Add docstring to get_dpkg_architecture</content>
</entry>
<entry>
<title>Ensure util.get_architecture() runs only once (#172)</title>
<updated>2020-01-16T17:29:59+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2020-01-16T17:29:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=259d9c501472315e539701f00095743390eb89e5'/>
<id>urn:sha1:259d9c501472315e539701f00095743390eb89e5</id>
<content type='text'>
* Ensure util.get_architecture() runs only once

util.get_architecture() recently was wrapped using python3's lru_cache()
which will cache the result so we only invoke 'dpkg --print-architecture'
once.  In practice, cloud-init.log will show multiple invocations of the
command.  The source of this was that the debian Distro object implements
the get_primary_arch() with this command, but it was not calling it from
util, but issuing a util.subp() directly.  This branch also updates
cc_apt_configure methods to fetch the arch value from the distro class,
and then ensure that the methods apt_configure calls pass the arch value
around.

* utils: remove lsb_release and get_architecture wrappers

The original lsb_release wrapper was used to prevent polluting the
single value we cached, however lru_cache() already handles this
case by using args, kwargs values to cache different calls to the
method.

* rename_apt_list: use all positional parameters</content>
</entry>
</feed>
