[api-ref] Fix nocatalog description for unscoped token

Unscoped token body never contains catalog, no matter the
nocatalog parameter is True or False.

This patch fixed the api-ref issue.

Change-Id: Ic3a09e3b25c20c5ac840f82631a1da1cbd1eb281
This commit is contained in:
wangxiyuan 2019-05-23 15:20:13 +08:00
parent d5da988792
commit a38dcfe99d
2 changed files with 11 additions and 4 deletions

View File

@ -128,7 +128,7 @@ Parameters
.. rest_parameters:: parameters.yaml
- nocatalog: nocatalog
- nocatalog: request_nocatalog_unscoped_path_not_required
- domain: domain
- name: user_name
- auth: auth
@ -329,7 +329,7 @@ Parameters
.. rest_parameters:: parameters.yaml
- nocatalog: nocatalog
- nocatalog: request_nocatalog_unscoped_path_not_required
- name: user_name
- auth: auth
- user: user
@ -404,7 +404,7 @@ Parameters
.. rest_parameters:: parameters.yaml
- nocatalog: nocatalog
- nocatalog: request_nocatalog_unscoped_path_not_required
- identity: identity
- token: auth_token
- id: auth_token_id
@ -590,7 +590,7 @@ Parameters
.. rest_parameters:: parameters.yaml
- nocatalog: nocatalog
- nocatalog: request_nocatalog_unscoped_path_not_required
- methods: auth_methods_token
- auth: auth
- token: auth_token

View File

@ -358,6 +358,13 @@ region_id_query:
in: query
required: false
type: string
request_nocatalog_unscoped_path_not_required:
description: |
(Since v3.1) nocatalog only works for scoped token. For unscoped token, the
authentication response always excludes the service catalog.
in: query
required: false
type: string
resource_name_query:
description: |
Filters the response by a specified resource name.