<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/warnings.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>2021-12-16T02:16:38+00:00</updated>
<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>pylint: Fix pylint warnings reported in pylint 2.0.0.</title>
<updated>2018-07-21T15:30:58+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-07-21T15:30:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=2a9d6203d946484cbe24297fe0e48a42a800756a'/>
<id>urn:sha1:2a9d6203d946484cbe24297fe0e48a42a800756a</id>
<content type='text'>
Pylint 2.0.0 was recently released and complains more about
logging-not-lazy than it used to.  I've fixed those warnings, here.

The changes in rh_subscription are more extensive.  pylint may be
complaining incorrectly there, but the tests were not correctly un-doing
all of their mock/patching.  This cleans those up and makes pylint happy.
</content>
</entry>
<entry>
<title>pylint: fix all logging warnings</title>
<updated>2017-04-21T14:14:47+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2017-04-06T18:14:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=5afe4cd0797a12d07ea19b9715b720d47bdea401'/>
<id>urn:sha1:5afe4cd0797a12d07ea19b9715b720d47bdea401</id>
<content type='text'>
This will change all instances of LOG.warn to LOG.warning as warn
is now a deprecated method. It will also make sure any logging
uses lazy logging by passing string format arguments as function
parameters.
</content>
</entry>
<entry>
<title>Support warning if the used datasource is not in ds-identify's list.</title>
<updated>2017-03-03T06:30:15+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-03-01T20:50:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=79db2e2436d91510aceb8c036c4a945362c85a52'/>
<id>urn:sha1:79db2e2436d91510aceb8c036c4a945362c85a52</id>
<content type='text'>
If ds-identify is in report mode, and the datasource that is found
is not in the list, then warn the user of this situation.
</content>
</entry>
<entry>
<title>Move warning functionality to cloudinit/warnings.py</title>
<updated>2017-03-03T06:30:15+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-02-28T22:14:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ade8c2e0266b020089145075e8236b95c000a3cb'/>
<id>urn:sha1:ade8c2e0266b020089145075e8236b95c000a3cb</id>
<content type='text'>
This moves the warning code that was added specifically for
EC2 into a generic path at cloudinit/warnings.py.

It also adds support for writing warning files into the
warnings directory to be shown by Z99-cloudinit-warnings.sh.
</content>
</entry>
</feed>
