From 24c5e6f2969b736f76a53cbd995c19613bb89e04 Mon Sep 17 00:00:00 2001 From: Adam Spiers Date: Mon, 5 Aug 2019 18:58:50 +0100 Subject: [PATCH] Don't claim that CLI user data requires manual base64 encoding python-novaclient automatically encodes user data as base64 before passing to the API, so don't claim that the user needs to do it, as discussed on IRC: http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2019-08-05.log.html#t2019-08-05T17:52:41 (Even they did need to, it would have been more helpful to tell them *how*.) Change-Id: I20c272e0a5b277652e1cef90d1f9fbb714e173d7 --- doc/source/user/metadata.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/source/user/metadata.rst b/doc/source/user/metadata.rst index 314c82a6911f..7a3fe8b6a595 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,