openstack/designate
Code Issues Proposed changes

Fix indentation of user documentation code blocks

Browse Source 
This removes unnecessary quotes to the left of code blocks.

Change-Id: I759b5c15c857e6dc4397ab3947ce8696421a75ce
This commit is contained in:
Pierre Riteau 2023-08-02 13:19:27 +02:00
parent 7d622d374d
commit 031eb8b5d3
2 changed files with 209 additions and 209 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/user/manage-recordsets.rst
View File

@ -56,7 +56,7 @@ To recreate the earlier example using the OpenStack client with the Designate
plugin, the user would run:
.. code-block:: console
.. code-block:: console
$ openstack recordset create --type A --record 192.0.2.1 example.org. www
+-------------+--------------------------------------+
@ -87,7 +87,7 @@ You can supply the ``--record`` argument multiple times to create multiple
records within the recordset. A typical use for this is `Round-robin DNS`_.
.. code-block:: console
.. code-block:: console
$ openstack recordset create --type A --record 192.0.2.1 --record 192.0.2.2 example.org. web
+-------------+--------------------------------------+
@ -113,7 +113,7 @@ records within the recordset. A typical use for this is `Round-robin DNS`_.
You can view the recordsets for a zone using the ``openstack recordset list``
command:
.. code-block:: console
.. code-block:: console
$ openstack recordset list example.org.
+--------------------------------------+------------------+------+---------------------------------------------------------------------+--------+--------+
@ -133,7 +133,7 @@ The authoritative nameserver for the zone is listed as the record data for the
``NS`` type record of the zone, which in this example is ``ns1.example.net.``.
To verify this you can query the nameserver using ``dig`` for the ``NS`` type:
.. code-block:: console
.. code-block:: console
$ dig @ns1.example.net example.org. -t NS +short
ns1.devstack.org.
@ -141,7 +141,7 @@ To verify this you can query the nameserver using ``dig`` for the ``NS`` type:
You can also verify the ``A`` recordsets. You don't need the ``-t`` option
because it is the default:
.. code-block:: console
.. code-block:: console
$ dig @ns1.example.net web.example.org. +short
192.0.2.2
@ -161,7 +161,7 @@ and unescaped double quotation marks as in RFC1035 section 5.1.
For example, to create a ``TXT`` record made of one string of 410
characters you can split it into 2 to like this:
.. code-block:: console
.. code-block:: console
$ openstack recordset create --type TXT --record '"210 characters string" "200 characters string"' example.org. _domainkey
@ -174,7 +174,7 @@ OpenStack commands, you can also use recordset ID. For example, to update
the recordset ``www.example.org.`` to contain two records, you could use
the following:
.. code-block:: console
.. code-block:: console
$ openstack recordset set example.org. www.example.org. --record 192.0.2.1 --record 192.0.2.2
+-------------+--------------------------------------+
@ -203,7 +203,7 @@ Deleting a recordset
You can use the ``openstack recordset delete`` command to remove recordsets
using the zone and either the FQDN or the recordset ID.
.. code-block:: console
.. code-block:: console
$ openstack recordset delete example.org. web.example.org.
+-------------+--------------------------------------+

12
doc/source/user/manage-zones.rst
View File

@ -57,7 +57,7 @@ Creating a zone
Creating a zone requires only the name of the zone and an email address of the
party responsible for the zone.
.. code-block:: console
.. code-block:: console
$ openstack zone create --email dnsmaster@example.com example.com.
+----------------+--------------------------------------+
@ -86,7 +86,7 @@ Note that the state is PENDING. Designate has received the request to create
the zone, but may not have completed it yet. After a short time, verify
successful creation of the DNS Zone:
.. code-block:: console
.. code-block:: console
$ openstack zone list
+--------------------------------------+--------------+---------+------------+--------+--------+
@ -97,7 +97,7 @@ successful creation of the DNS Zone:
There will now be two recordsets visible in the zone:
.. code-block:: console
.. code-block:: console
$ openstack recordset list example.com.
+--------------------------------------+--------------+------+---------------------------------------------------------------------+--------+--------+
@ -111,7 +111,7 @@ The values for refresh, retry, minimum and expire on the SOA record are set by
the Designate operator. The TTL, however, can be modified by users via the
zone:
.. code-block:: console
.. code-block:: console
$ openstack zone set example.com. --ttl 3000
+----------------+--------------------------------------+
@ -140,7 +140,7 @@ The ``dig`` tool can be used to query one of the backend nameservers to confirm
the result. In this example, there is a DNS server at ``192.168.122.186``
managed by designate as part of the default pool.
.. code-block:: console
.. code-block:: console
$ dig @192.168.122.186 example.com.
@ -174,7 +174,7 @@ Deleting a zone
A zone can be deleted using either its name or ID:
.. code-block:: console
.. code-block:: console
$ openstack zone delete example.com.
+----------------+--------------------------------------+