diff --git a/api-ref/src/wadls/orchestration-api/src/v1/orchestration-api.wadl b/api-ref/src/wadls/orchestration-api/src/v1/orchestration-api.wadl index c68a8e0d7..1e4aa1e82 100644 --- a/api-ref/src/wadls/orchestration-api/src/v1/orchestration-api.wadl +++ b/api-ref/src/wadls/orchestration-api/src/v1/orchestration-api.wadl @@ -320,9 +320,8 @@ - Filters the stack list by a stack ID. - Use this filter multiple times to filter - by multiple IDs. + Filters the stack list by a stack ID. Use this filter + multiple times to filter by multiple IDs. @@ -330,9 +329,8 @@ - Filters the stack list by a status. - Use this filter multiple times to filter - by multiple statuses. + Filters the stack list by a status. Use this filter + multiple times to filter by multiple statuses. @@ -340,8 +338,8 @@ - Filters the stack list by a name. - Use this filter multiple times to filter by multiple names. + Filters the stack list by a name. Use this filter multiple + times to filter by multiple names. @@ -387,17 +385,17 @@ - Specifies whether to include deleted stacks in the list. + Set to True to include deleted stacks in the list. Default is False, which excludes deleted stacks from the list. - + - Specifies whether to include nested stacks in the list. + Set to True to include nested stacks in the list. Default is False, which excludes nested stacks from the list. @@ -462,7 +460,7 @@ - Specifies whether to include stacks from all tenants in + Set to True to include stacks from all tenants in the stack list. Specify policy requirements in the Orchestration policy.json file. Default is False. @@ -473,7 +471,7 @@ - Specifies whether to include a count key in the response. + Set to True to include a count key in the response. The count key value is the number of stacks that match the query criteria. Default is False. @@ -493,7 +491,8 @@ &intServerErr; - Creates a stack. @@ -630,7 +629,7 @@ - A reference to the stack's parent. If no parent, + A reference to the parent of the stack. If no parent, reference is self. @@ -774,8 +773,8 @@ - Time of last stack update in the following format: YYYY-MM-DDThh:mm:ssTZD, where TZD is + Time of last stack update in the following format: + YYYY-MM-DDThh:mm:ssTZD, where TZD is the time zone designator. @@ -1015,12 +1014,13 @@ Finds the canonical URL for a stack. - Also works with verbs other than &GET;, so you can perform &PUT; - and &DELETE; operations on a current stack. Set your client to - follow redirects. Note that when redirecting, the request method - should not change, as defined in RFC2626. However, in many clients - the default behavior is to change the method to &GET; when you - receive a 302 because this behavior is ubiquitous in web browsers. + Also works with verbs other than &GET;, so that you can perform + &PUT; and &DELETE; operations on a current stack. Set your client + to follow redirects. When redirecting, the request method should + not change as defined in RFC2626. However, in many clients the + default behavior is to change the method to &GET; when you receive + a 302 response code because this behavior is + ubiquitous in web browsers. @@ -1066,7 +1066,9 @@ - Returns the template for a stack. + + Returns the template for a stack. + @@ -1094,7 +1096,8 @@ &environmentParameterOptional; &filesParameter; &tagsParameter; - + @@ -1109,14 +1112,14 @@ of this parameter. In the example, a and b are the names of two parameters defined in the template. - { ... + + { ... "parameters": { "a": "Value", "b": "3" } ... } - - + While the service accepts JSON numbers for parameters with the type number and JSON objects for parameters @@ -1153,48 +1156,49 @@ &intServerErr; - + Previews an update for a stack. - - - - - - - &templateUrlParameter; - &templateParameter; - &environmentParameterOptional; - &filesParameter; - &tagsParameter; - - - - This parameter supplies updated arguments for - parameters defined in the stack template. - - - The value is a JSON object, where each key is the name of a - parameter defined in the template and the associated value - is the argument to use for that parameter when instantiating - the template. The following code shows the general structure - of this parameter. In the example, a and - b are the names of two parameters defined in - the template. - { ... + + + + + + + &templateUrlParameter; + &templateParameter; + &environmentParameterOptional; + &filesParameter; + &tagsParameter; + + + + Supplies updated arguments for parameters that are + defined in the stack template. + + + The value is a JSON object, where each key is the name of + a parameter defined in the template and the associated + value is the argument to use for that parameter when + instantiating the template. The following code shows the + general structure of this parameter. In the example, + a and b are the names of two + parameters defined in the template. + + { ... "parameters": { "a": "Value", "b": "3" } ... } - - - + + While the service accepts JSON numbers for parameters with the type number and JSON objects for parameters with the type json, all parameter values are @@ -1479,20 +1483,45 @@ + + + + Filters the response by a resource type name. You can set + this value to a regular expression. Use this filter + multiple times to filter by multiple names. + + + + + + + Filters the response by resource types by heat version. + For example, 2015.1 or 5.0.0. + Use this filter multiple times to filter by multiple + versions. + + + - - - Filters the resource types by a support status. Valid - support status values are UNKNOWN, - SUPPORTED, DEPRECATED, - UNSUPPORTED, and HIDDEN. Use this - filter multiple times to filter by multiple support - statuses. - - + + + Filters the response by resource types by a support + status. Valid support status values are + UNKNOWN, SUPPORTED, + DEPRECATED, UNSUPPORTED, and + HIDDEN. Use this filter multiple times to + filter by multiple support statuses. + +