summaryrefslogtreecommitdiff
path: root/packages
diff options
context:
space:
mode:
authorxiaofengw-vmware <42736879+xiaofengw-vmware@users.noreply.github.com>2020-07-21 23:52:29 +0800
committerGitHub <noreply@github.com>2020-07-21 09:52:29 -0600
commit995f8adf00509e5d2aefc9f0680c3c4894ae6666 (patch)
tree77d3f08cd1fe9280ef509240000cc35e55dd7037 /packages
parentebc145be5e15c64a31ba496625727a7308a57baf (diff)
downloadvyos-cloud-init-995f8adf00509e5d2aefc9f0680c3c4894ae6666.tar.gz
vyos-cloud-init-995f8adf00509e5d2aefc9f0680c3c4894ae6666.zip
VMware: Support parsing DEFAULT-RUN-POST-CUST-SCRIPT (#441)
Add support for VMware's vCD configuration setting DEFAULT-RUN-POST-CUST-SCRIPT. When set True, it will default vms to run post customization scripts if the VM has not been configured in VMTools with "enable-custom-scripts" set False. Add datasource documentation with a bit more context about this interaction on VMware products. With this fix, the behavior will be: * If VM administrator doesn't want others to execute a script on this VM, VMtools can set "enable-custom-scripts" to false from the utility "vmware-toolbox-cmd". * If VM administrator doesn't set value to "enable-custom-scripts", then by default this script is disabled for security purpose. * For VMware's vCD product , the preference is to enable the script if "enable-custom-scripts" is not set. vCD will generate a configuration file with "DEFAULT-RUN-POST-CUST-SCRIPT" set to true. This flag works for both VMware customization engine and cloud-init.
Diffstat (limited to 'packages')
0 files changed, 0 insertions, 0 deletions