This seems to work to run the user-data part of cloud-init, so that's great.
However the problem seems to be that the Customization script must now include the network configuration as well - so either I have to find a way to generate the script dynamically or maybe find a way that *all* customization is done through cloud-init.
Is there a way to just completely turn off any customization?
I tried to use:
vmware-toolbox-cmd config set deployPkg enable-custom-scripts false
vmware-toolbox-cmd config set deployPkg enable-customization false
But it seems that even with those 2 commands it is still trying to run the customizations.
This seems to work to run the user-data part of cloud-init, so that's great.
However the problem seems to be that the Customization script must now include the network configuration as well - so either I have to find a way to generate the script dynamically or maybe find a way that *all* customization is done through cloud-init.
Is there a way to just completely turn off any customization?
I tried to use:
vmware-toolbox-cmd config set deployPkg enable- custom- scripts false customization false
vmware-toolbox-cmd config set deployPkg enable-
But it seems that even with those 2 commands it is still trying to run the customizations.