summaryrefslogtreecommitdiff
path: root/doc/rtd/topics
diff options
context:
space:
mode:
authorDan Kenigsberg <danken@redhat.com>2021-01-21 17:17:57 +0200
committerGitHub <noreply@github.com>2021-01-21 09:17:57 -0600
commite051d54227b153e19774775edf475425e6ebabd8 (patch)
tree8eff0336593d558159e2adc27a69005aee71fb31 /doc/rtd/topics
parentb3abcdc09b894249c8360a030d8aa3b815bd0c20 (diff)
downloadvyos-cloud-init-e051d54227b153e19774775edf475425e6ebabd8.tar.gz
vyos-cloud-init-e051d54227b153e19774775edf475425e6ebabd8.zip
doc: avoid two warnings (#781)
Two shell code blocks are not marked as such, confusing rst to consider them as yaml. Be explicit about their syntax, and use $ prompt to match elsewhere in the docs. /home/travis/build/canonical/cloud-init/doc/rtd/topics/format.rst:28: WARNING: Could not lex literal_block as "yaml". Highlighting skipped. /home/travis/build/canonical/cloud-init/doc/rtd/topics/format.rst:52: WARNING: Could not lex literal_block as "yaml". Highlighting skipped. Signed-off-by: Dan Kenigsberg <danken@redhat.com>
Diffstat (limited to 'doc/rtd/topics')
-rw-r--r--doc/rtd/topics/format.rst14
1 files changed, 9 insertions, 5 deletions
diff --git a/doc/rtd/topics/format.rst b/doc/rtd/topics/format.rst
index d03e4caf..fa8aa925 100644
--- a/doc/rtd/topics/format.rst
+++ b/doc/rtd/topics/format.rst
@@ -23,9 +23,11 @@ Using a mime-multi part file, the user can specify more than one type of data.
For example, both a user data script and a cloud-config type could be
specified.
-Supported content-types are listed from the cloud-init subcommand make-mime::
+Supported content-types are listed from the cloud-init subcommand make-mime:
- % cloud-init devel make-mime --list-types
+.. code-block:: shell-session
+
+ $ cloud-init devel make-mime --list-types
cloud-boothook
cloud-config
cloud-config-archive
@@ -47,9 +49,11 @@ The cloud-init subcommand can generate MIME multi-part files: `make-mime`_.
separated by a colon (e.g. ``config.yaml:cloud-config``) and emits a MIME
multipart message to stdout. An example invocation, assuming you have your
cloud config in ``config.yaml`` and a shell script in ``script.sh`` and want
-to store the multipart message in ``user-data``::
+to store the multipart message in ``user-data``:
+
+.. code-block:: shell-session
- % cloud-init devel make-mime -a config.yaml:cloud-config -a script.sh:x-shellscript > user-data
+ $ cloud-init devel make-mime -a config.yaml:cloud-config -a script.sh:x-shellscript > user-data
.. _make-mime: https://github.com/canonical/cloud-init/blob/master/cloudinit/cmd/devel/make_mime.py
@@ -70,7 +74,7 @@ archive.
Example
-------
-::
+.. code-block:: shell-session
$ cat myscript.sh