vyos-cloud-init.git/cloudinit/distros/sles.py, branch rolling

Adopt Black and isort (SC-700) (#1157)

2021-12-16T02:16:38+00:00

Applied Black and isort, fixed any linting issues, updated tox.ini and CI.

cloudinit: remove unused LOG variables (#574)

2020-09-16T13:53:09+00:00

Co-authored-by: Rick Harding

suse: Add support for openSUSE and return SLES to a working state.

2017-08-30T17:39:47+00:00

This gets initial opensuse and SLES support back to a working state. Still missing is more complete network file writing and unit tests.

LICENSE: Allow dual licensing GPL-3 or Apache 2.0

2016-12-22T22:04:28+00:00

This has been a recurring ask and we had initially just made the change to the cloud-init 2.0 codebase. As the current thinking is we'll just continue to enhance the current codebase, its desirable to relicense to match what we'd intended as part of the 2.0 plan here. - put a brief description of license in LICENSE file - put full license versions in LICENSE-GPLv3 and LICENSE-Apache2.0 - simplify the per-file header to reference LICENSE - tox: ignore H102 (Apache License Header check) Add license header to files that ship. Reformat headers, make sure everything has vi: at end of file. Non-shipping files do not need the copyright header, but at the moment tests/ have it.

Low hanging Python 3 fruit.

2015-01-23T02:21:04+00:00

Largely merge lp:~harlowja/cloud-init/py2-3 albeit manually because it seemed

2015-01-21T22:56:53+00:00

to be behind trunk. `tox -e py27` passes full test suite. Now to work on replacing mocker.

hostname: apply hostname same as is written

2015-01-16T19:29:48+00:00

on RHEL, we were writing to persistent configuration the fqdn, but invoking 'hostname' on the first boot with just the shortname. On 'reboot', then the hostname would differ. Now, whatever we write, invoke hostname with. Also remove some duplicate code. LP: #1246485

remove some white space

2014-01-23T19:06:13+00:00

Split net-parsing into own module

2014-01-22T20:04:39+00:00

The ubuntu/debian networking file parsing function really is more generic than just a rhel utility function and can be used by others that want to use this functionality for there own purposes (say in writing down a freebsd network format instead) so moving this to its own module to encourage its usage outside of rhel.

fix pep8 and pylint warnings

2013-08-06T10:36:30+00:00