Skip to content

Commit 3297268

Browse files
committed
Update Blog “how-to-use-dscc-api-and-ansible-to-collect-the-storage-configuration”
1 parent 9d01867 commit 3297268

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

content/blog/how-to-use-dscc-api-and-ansible-to-collect-the-storage-configuration.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,13 +64,15 @@ The below code example had the client credentials stored in the credentials.yml
6464
6565
## DSCC REST API call
6666
67-
A DSCC REST API call can be with and without a request body and can have multiple responses depending on the actual API call. Nevertheless, it is good practice to build a modular code approach that uses a generalized REST API call to access the Data Services Cloud Console. The generalized DSCC REST API call has its parameters:
67+
A DSCC REST API call can be with and without a request body and can have multiple responses depending on the actual API call. Nevertheless, it is good practice to build a modular code approach that uses a generalized REST API call to access the Data Services Cloud Console. The generalized DSCC REST API call, shown in the following cade block, has its parameters:
68+
69+
6870
6971
* requestUri (as mentioned in the [](https://developer.hpe.com/greenlake/data-services-on-the-hpe-greenlake-platform/home/)[Data Services REST API](https://console-us1.data.cloud.hpe.com/doc/api/v1/))
7072
* request method (Get, Post, Delete, Put)
7173
* request body (optional)
7274
73-
and is shown in the following code block:
75+
7476
7577
```yaml
7678
- name: Include encrypted vars

0 commit comments

Comments
 (0)