Skip to content

Commit 00fa8b4

Browse files
committed
Update Blog “converting-hpe-greenlake-api-specifications-in-oas-3-1-using-openapi-tools”
1 parent 867fcaa commit 00fa8b4

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

content/blog/converting-hpe-greenlake-api-specifications-in-oas-3-1-using-openapi-tools.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,13 @@ Commands:
132132

133133
Don't worry because I am not going to leave you stranded! 😊
134134

135-
At this point, we have the required tools to create the pipeline for the conversion from the OpenAPI Standard 3.1 spec files to the client library for my choice of scripting languages. The process will be in a sequence from downloading the OpenAPI spec file from the HPE GreenLake developer website, convert that spec file to OpenAPI Standard 3.0 spec file, and then convert that 3.0 spec file to the client library. Let me give you an example for converting the HPE GreenLake API for Data Services file spec to a PowerShell client library.
135+
Now we have the required tools to create a pipeline to convert from the OpenAPI Standard 3.1 spec files to the client library for the scripting language of choice. An overview of the process:
136+
137+
1. Download the OpenAPI spec file from the HPE GreenLake developer website.
138+
2. Convert the spec file to OpenAPI Standard 3.0 spec file.
139+
3. Convert the 3.0 spec file to the client library.
140+
141+
Let me give you an example of converting the HPE GreenLake API for Data Services spec file to a PowerShell client library.
136142

137143
1. I downloaded the HPE GreenLake API for Data Services OpenAPI Standard 3.1 spec file from the HPE GreenLake Developer website using the UI shown below:
138144

0 commit comments

Comments
 (0)