summaryrefslogtreecommitdiff
path: root/doc/source/cli/command-objects/application-credentials.rst
diff options
context:
space:
mode:
authorEric Fried <openstack@fried.cc>2019-11-04 17:16:34 -0600
committerMonty Taylor <mordred@inaugust.com>2020-06-08 16:34:27 -0500
commit26878e7d53a531adb67c9ddde8fd6d3c3092ce34 (patch)
tree1ebf5ccc543312981f9861fb21e813959f82d2fd /doc/source/cli/command-objects/application-credentials.rst
parent00e88822e3fcb288d9fe8d019ee7d1bf8dd74630 (diff)
downloadpython-openstackclient-26878e7d53a531adb67c9ddde8fd6d3c3092ce34.tar.gz
identity: autogenerate docs
$namespace = openstack.identity.v{2|3} The subcommand documents for $namespace were hardcoded and thus prone to drift over time. This commit removes the hardcoded content and uses the autoprogram-cliff directive to generate them automatically from the subcommand configuration classes. Special things: - Some reorganization happened here. Certain subcommand names, such as `endpoint` and `project`, are shared by identify v2 and v3. Previously the hardcoded documents had them combined and interleaved. Attempting to preserve this with autoprogram-cliff would have required significant additional infrastructure. However, since most readers care completely about one and not at all about the other, we instead split the v2 and v3 versions of these commands into separate pages. In case links to the old pages exist in the wild, they are preserved, but moved (with redirects) to a hidden directory, and populated simply with links to the new version-specific generated documents. - The `federation domain` and `federation project` subcommands were previously absent from the docs. They are added. These are such small commands and they seem related, so they're put into a single document. - Some pages were already being generated but were listing operations individually instead of using wildcards (possibly because they were created before wildcarding was supported by cliff). These are changed to use wildcarding. (We want to do this wherever possible as it is more future-proof in the event that more operations are added to a subcommand later.) - The `service provider` document was incorrectly titled `identity provider`. Fixed. Change-Id: I2030f9fe370038c5908b6eb6bed9692a73fe5067
Diffstat (limited to 'doc/source/cli/command-objects/application-credentials.rst')
-rw-r--r--doc/source/cli/command-objects/application-credentials.rst107
1 files changed, 2 insertions, 105 deletions
diff --git a/doc/source/cli/command-objects/application-credentials.rst b/doc/source/cli/command-objects/application-credentials.rst
index 047f5ab6..cef3ef0d 100644
--- a/doc/source/cli/command-objects/application-credentials.rst
+++ b/doc/source/cli/command-objects/application-credentials.rst
@@ -8,109 +8,6 @@ With application credentials, a user can grant their applications limited
access to their cloud resources. Once created, users can authenticate with an
application credential by using the ``v3applicationcredential`` auth type.
-application credential create
------------------------------
-Create new application credential
-
-.. program:: application credential create
-.. code:: bash
-
- openstack application credential create
- [--secret <secret>]
- [--role <role>]
- [--expiration <expiration>]
- [--description <description>]
- [--restricted|--unrestricted]
- [--access-rules <access-rules>]
- <name>
-
-.. option:: --secret <secret>
-
- Secret to use for authentication (if not provided, one will be generated)
-
-.. option:: --role <role>
-
- Roles to authorize (name or ID) (repeat option to set multiple values)
-
-.. option:: --expiration <expiration>
-
- Sets an expiration date for the application credential (format of
- YYYY-mm-ddTHH:MM:SS)
-
-.. option:: --description <description>
-
- Application credential description
-
-.. option:: --unrestricted
-
- Enable application credential to create and delete other application
- credentials and trusts (this is potentially dangerous behavior and is
- disabled by default)
-
-.. option:: --restricted
-
- Prohibit application credential from creating and deleting other
- application credentials and trusts (this is the default behavior)
-
-.. option:: --access-rules
-
- Either a string or file path containing a JSON-formatted list of access
- rules, each containing a request method, path, and service, for example
- '[{"method": "GET", "path": "/v2.1/servers", "service": "compute"}]'
-
-.. describe:: <name>
-
- Name of the application credential
-
-
-application credential delete
------------------------------
-
-Delete application credential(s)
-
-.. program:: application credential delete
-.. code:: bash
-
- openstack application credential delete
- <application-credential> [<application-credential> ...]
-
-.. describe:: <application-credential>
-
- Application credential(s) to delete (name or ID)
-
-application credential list
----------------------------
-
-List application credentials
-
-.. program:: application credential list
-.. code:: bash
-
- openstack application credential list
- [--user <user>]
- [--user-domain <user-domain>]
-
-.. option:: --user
-
- User whose application credentials to list (name or ID)
-
-.. option:: --user-domain
-
- Domain the user belongs to (name or ID). This can be
- used in case collisions between user names exist.
-
-application credential show
----------------------------
-
-Display application credential details
-
-.. program:: application credential show
-.. code:: bash
-
- openstack application credential show
- <application-credential>
-
-.. describe:: <application-credential>
-
- Application credential to display (name or ID)
+.. autoprogram-cliff:: openstack.identity.v3
+ :command: application credential *