summaryrefslogtreecommitdiff
path: root/doc/examples/cloud-config-vendor-data.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/examples/cloud-config-vendor-data.txt')
-rw-r--r--doc/examples/cloud-config-vendor-data.txt16
1 files changed, 0 insertions, 16 deletions
diff --git a/doc/examples/cloud-config-vendor-data.txt b/doc/examples/cloud-config-vendor-data.txt
deleted file mode 100644
index 7f90847b..00000000
--- a/doc/examples/cloud-config-vendor-data.txt
+++ /dev/null
@@ -1,16 +0,0 @@
-#cloud-config
-#
-# This explains how to control vendordata via a cloud-config
-#
-# On select Datasources, vendors have a channel for the consumptions
-# of all support user-data types via a special channel called
-# vendordata. Users of the end system are given ultimate control.
-#
-vendor_data:
- enabled: True
- prefix: /usr/bin/ltrace
-
-# enabled: whether it is enabled or not
-# prefix: the command to run before any vendor scripts.
-# Note: this is a fairly weak method of containment. It should
-# be used to profile a script, not to prevent its run