summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZuul <zuul@review.opendev.org>2019-11-22 20:58:10 +0000
committerGerrit Code Review <review@openstack.org>2019-11-22 20:58:10 +0000
commit8cbe9939d2120b8ffd93273fae6998094b7f7c6e (patch)
tree430a30e9fbd07d9930bbd3cd4fd9090bb59d6f2d
parent58fba4f8854d830b9513544debd24a316a2e6e4f (diff)
parent24c5e6f2969b736f76a53cbd995c19613bb89e04 (diff)
downloadnova-8cbe9939d2120b8ffd93273fae6998094b7f7c6e.tar.gz
Merge "Don't claim that CLI user data requires manual base64 encoding"
-rw-r--r--doc/source/user/metadata.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/source/user/metadata.rst b/doc/source/user/metadata.rst
index 314c82a691..7a3fe8b6a5 100644
--- a/doc/source/user/metadata.rst
+++ b/doc/source/user/metadata.rst
@@ -427,8 +427,9 @@ You can place user data in a local file and pass it through the ``--user-data
.. note::
- The provided user data must be base64 encoded and is restricted to 65535
- bytes.
+ The provided user data should not be base64-encoded, as it will be
+ automatically encoded in order to pass valid input to the REST
+ API, which has a limit of 65535 bytes after encoding.
Once booted, you can access this data from the instance using either the
metadata service or the config drive. To access it via the metadata service,