diff options
author | Scott Moser <smoser@ubuntu.com> | 2014-01-15 15:42:02 -0500 |
---|---|---|
committer | Scott Moser <smoser@ubuntu.com> | 2014-01-15 15:42:02 -0500 |
commit | 42f2cffadabfefb0469ade2f1f1c3ce5edabc9fa (patch) | |
tree | 178e0c61cc80942263a73d5c5ce3578118a261be /config | |
parent | 0588ecd6adc9144bc911000a47a1f7ed27ea8aed (diff) | |
download | vyos-cloud-init-42f2cffadabfefb0469ade2f1f1c3ce5edabc9fa.tar.gz vyos-cloud-init-42f2cffadabfefb0469ade2f1f1c3ce5edabc9fa.zip |
remove vendor-scripts-per-{boot,instance,once}
I don't see a real need for these. The intent of the 'per-boot' or
'per-instance' or 'per-once' config modules is to handle running
scripts that were already inserted into the instance.
If the vendor is doing that, then there is value in vendor-data.
Ie, they'd already modified the image, they might as well have just
put the stuff in that they wanted.
Diffstat (limited to 'config')
-rw-r--r-- | config/cloud.cfg | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/config/cloud.cfg b/config/cloud.cfg index 8ed3522d..b746e3db 100644 --- a/config/cloud.cfg +++ b/config/cloud.cfg @@ -64,9 +64,6 @@ cloud_config_modules: # The modules that run in the 'final' stage cloud_final_modules: - rightscale_userdata - - vendor-scripts-per-once - - vendor-scripts-per-boot - - vendor-scripts-per-instance - scripts-vendor - scripts-per-once - scripts-per-boot |