<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tests/unittests/test_vmware, branch 20.3</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=20.3</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.3'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2020-06-08T16:49:12+00:00</updated>
<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>VMWware: support to update guest info gc status if enabled (#261)</title>
<updated>2020-03-26T16:31:04+00:00</updated>
<author>
<name>xiaofengw-vmware</name>
<email>42736879+xiaofengw-vmware@users.noreply.github.com</email>
</author>
<published>2020-03-26T16:31:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1fefeef92fd1881b21e124b83f2adefd3e014087'/>
<id>urn:sha1:1fefeef92fd1881b21e124b83f2adefd3e014087</id>
<content type='text'>
</content>
</entry>
<entry>
<title>guestcust_util: handle special characters in config file</title>
<updated>2019-10-17T15:18:44+00:00</updated>
<author>
<name>Xiaofeng Wang</name>
<email>xiaofengw@vmware.com</email>
</author>
<published>2019-10-17T15:18:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ecb501b84338f078be18c38c68c3ce87fed3584b'/>
<id>urn:sha1:ecb501b84338f078be18c38c68c3ce87fed3584b</id>
<content type='text'>
Handle the special characters when reading VM Tools configure file.
For example, the key and value may contain _, - and . etc.
</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>VMWare: Trigger the post customization script via cc_scripts module.</title>
<updated>2019-07-16T13:09:38+00:00</updated>
<author>
<name>Xiaofeng Wang</name>
<email>xiaofengw@vmware.com</email>
</author>
<published>2019-07-16T13:09:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=9c47c682b7aaa185c32a68f4dea8e23e9a2ef565'/>
<id>urn:sha1:9c47c682b7aaa185c32a68f4dea8e23e9a2ef565</id>
<content type='text'>
cloud-init does not trigger reboots of a VM therefore adding custom
scripts to rc.local does not execute the post scripts.  This patch
moves post-scripts into per-instance scripts dir and has cc_scripts
module run the post-scripts.

Also in this branch:
  - Remove the sh interpreter and execute the customization script
    directly.
  - Update the unit test.

LP: #1833192
</content>
</entry>
<entry>
<title>VMware: Support for user provided pre and post-customization scripts</title>
<updated>2017-12-08T17:15:00+00:00</updated>
<author>
<name>Maitreyee Saikia</name>
<email>msaikia@vmware.com</email>
</author>
<published>2017-12-08T17:10:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ce33e423cde806a0590fec635778d62836e1bd37'/>
<id>urn:sha1:ce33e423cde806a0590fec635778d62836e1bd37</id>
<content type='text'>
In the VMware customization workflow, we have some options for the user
to upload scripts for additional customization. Based on user request,
those custom scripts can be either run before regular customization or
after. For post customization scripts, we decide whether to run the scripts
just after customization or post system reboot.
</content>
</entry>
</feed>
