Merge pull request #404 from rpscodes/master

Create new flows without Gogs

Author: hguerrero

docs/labs/developer-track/lab01/images/api-designer-get-post.png

@@ -67,15 +67,15 @@ Let's start verifying your API.
 
 . Time to verify our data definitions for the API. Click on the `+location/phone/{id}+` link under the _Paths_.
 +
-image::images/api-designer-location-path.png[api-designer-location-path, role="integr8ly-img-responsive"]
+image::images/api-designer-location-phone.png[api-designer-location-phone, role="integr8ly-img-responsive"]
 
 . Notice that this API path has a single path parameter (`id` defined as an `int32`) and a single GET operation defined.  Click on the GET operation, then click the location drop-down which is part of the 200 OK response.
 +
-image::images/api-dsigner-id-int32.png[api-dsigner-id-int32, role="integr8ly-img-responsive"]
+image::images/api-designer-path.png[api-designer-path, role="integr8ly-img-responsive"]
 
 . Notice that this API path has a single response defined (a `200 OK` response) and the type that is returned is a `location` object.
 +
-image::images/api-dsigner-location-response.png[api-dsigner-location-response, role="integr8ly-img-responsive"]
+image::images/api-designer-response.png[api-designer-response, role="integr8ly-img-responsive"]
 
 [type=verification]
 Did you verify the `200 OK` response returns a `location`?
@@ -87,17 +87,17 @@ Have your instructor check the Kubernetes pod that contains the API Designer app
 
 . Click on the `</> location` object link under the _Data Types_ section.  Notice that the object has a bunch of properties defined which make up the object.
 +
-image::images/api-designer-location-datatype.png[api-designer-location-datatype, role="integr8ly-img-responsive"]
+image::images/api-designer-location.png[api-designer-location, role="integr8ly-img-responsive"]
 
 . Click on the source link and notice that we have both YAML and JSON schemas generated by our object design:
 +
-image::images/api-designer-source.png[api-designer-source, role="integr8ly-img-responsive"]
+image::images/api-designer-json-yaml.png[api-designer-json-yaml, role="integr8ly-img-responsive"]
 
 === Step 4: Verify the /locations path
 
 . Click the */locations* path.  Then click on the source tab.  Notice that we have both a GET and POST request defined, together with a couple of example requests.  Using a POST method, we can insert a new record into our sample database with Fuse.
 +
-image::images/api-designer-locations-path-methods.png[api-designer-locations-path-methods, role="integr8ly-img-responsive"]
+image::images/api-designer-get-post.png[api-designer-get-post, role="integr8ly-img-responsive"]
 
 [type=verification]
 Did you locate the `get` and `post` requests in the source for `/locations`?