<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/sources/helpers/vmware/imc/guestcust_error.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>[VMware] Support cloudinit raw data feature (#691)</title>
<updated>2021-01-13T23:18:28+00:00</updated>
<author>
<name>xiaofengw-vmware</name>
<email>42736879+xiaofengw-vmware@users.noreply.github.com</email>
</author>
<published>2021-01-13T23:18:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=11630044d235e0c6e1ffd2b12ff8906613ccdac6'/>
<id>urn:sha1:11630044d235e0c6e1ffd2b12ff8906613ccdac6</id>
<content type='text'>
This feature will modify VMware datasource to read from meta data and user data which are specified by VMware vSphere user. If meta data/user data are found in cloud-init configuration directory, datasource will parse the meta data/network and user data from the configuration file, otherwise it will continue to parse them from traditional customization configuration file as before. The supported meta data file is in json or yaml format.</content>
</entry>
<entry>
<title>VMWware: add option into VMTools config to enable/disable custom script.</title>
<updated>2019-09-11T18:53:01+00:00</updated>
<author>
<name>Xiaofeng Wang</name>
<email>xiaofengw@vmware.com</email>
</author>
<published>2019-09-11T18:53:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=45426d8d38a7224962867ba71f390cce653e0d17'/>
<id>urn:sha1:45426d8d38a7224962867ba71f390cce653e0d17</id>
<content type='text'>
VMWware customization already has support to run a custom script during
the VM customization. Adding this option allows a VM administrator to
disable the execution of customization scripts.  If set the script
will not execute and the customization status is set to
GUESTCUST_ERROR_SCRIPT_DISABLED.
</content>
</entry>
<entry>
<title>LICENSE: Allow dual licensing GPL-3 or Apache 2.0</title>
<updated>2016-12-22T22:04:28+00:00</updated>
<author>
<name>Jon Grimm</name>
<email>jon.grimm@canonical.com</email>
</author>
<published>2016-11-22T23:09:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=b2a9f33616c806ae6e052520a8589113308f567c'/>
<id>urn:sha1:b2a9f33616c806ae6e052520a8589113308f567c</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>run flake8 instead of pyflakes in tox.  expect tests/ to pass flake8.</title>
<updated>2016-05-12T20:43:11+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2016-05-12T20:43:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=4ba4df2f00ab1763920280f76e2b4497898858af'/>
<id>urn:sha1:4ba4df2f00ab1763920280f76e2b4497898858af</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix up a ton of flake8 issues</title>
<updated>2016-05-12T17:56:26+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@gmail.com</email>
</author>
<published>2016-05-12T17:56:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=f11827aee59cf2678c3d2a157218a3fe2831f5c2'/>
<id>urn:sha1:f11827aee59cf2678c3d2a157218a3fe2831f5c2</id>
<content type='text'>
</content>
</entry>
<entry>
<title> - Ignored return code 1 for 'pkill' command in config_nic.py</title>
<updated>2016-03-08T20:41:08+00:00</updated>
<author>
<name>Sankar Tanguturi</name>
<email>stanguturi@stanguturi-rhel</email>
</author>
<published>2016-03-08T20:41:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ef7368ef61c47fbb0bc03e6e7a5bc4571d492baf'/>
<id>urn:sha1:ef7368ef61c47fbb0bc03e6e7a5bc4571d492baf</id>
<content type='text'>
 - Added few utility functions to report events to the underlying
   VMware Virtualization platform
 - Re-factored code little bit.
 - Executed ./tools/run-pep8 and no pep8 errors were reported.
</content>
</entry>
</feed>
