Skip to content

Commit 9d01867

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

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ The below code example had the client credentials stored in the credentials.yml
6767
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:
6868
6969
* 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/))
70-
* request method (GET, POST, DELETE, PUT)
70+
* request method (Get, Post, Delete, Put)
7171
* request body (optional)
7272
7373
and is shown in the following code block:

0 commit comments

Comments
 (0)