Merge pull request #528 from mulesoft/W-13725586-clarify-upstream-downstream-gr

W-13725586 clarify upstream downstream gr

Author: glenn-rodgers-sf

modules/ROOT/assets/image-source-files/api-upstream-downstream-config.graffle

@@ -33,7 +33,7 @@ instance.
 
 When you are promoting or importing an API instance, you do not have options to alter the configuration. However, when you add a new API instance, you need to the downstream and the upstream configuration settings.
 
-The following diagram shows the relationship of the upstream and downstream configurations settings to your upstream service and consumer application.
+The following diagram shows the relationship of the upstream and downstream configurations settings to your upstream service and the downstream consumer application. In this configuration, the downstream service is the service making API requests that are completed by the upstream service. These terms represent the direction of dependency, not the direction of information. A downstream service could make a `POST` request where it provides information to the upstream service. However, the downstream service is still dependent on the upstream service to complete the request.
 
 image:api-upstream-downstream-config.png[The API instance is deployed on a gateway between the upstream and downstream configuration]
 

modules/ROOT/assets/images/api-upstream-downstream-config.png

@@ -91,6 +91,17 @@ NOTE: After adding the API on Anypoint Platform, you will need to bind it to a s
 [arabic]
 .. Enter a name for the new API asset.
 //end::mid-steps[]
+//tag::asset-type-options-flex[]
+.. Select the **Asset type** from the following options:
+
+** **REST API:** Select this option if you have a RAML or OAS API definition file you want to include for your asset.
++
+Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are the recommended versions for OAS or RAML specs, because these versions add native OAS support. If you upload an OAS API specification to an API proxy version 1.0 or earlier, your API specification is translated to RAML.
+** **HTTP API:** Select this option if you do not have an API definition file you want to include for your asset.
+
+.. Optionally, you can add an **AssetId** and customize the **Version** or **API Version** details by clicking **Advanced**.
+. Click *Next*.
+//end::asset-type--options-flex[]
 //tag::asset-type-options[]
 .. Select the **Asset type** from the following options:
 

modules/ROOT/pages/_partials/task-add-api-instance.adoc

@@ -22,7 +22,7 @@ See xref:gateway::flex-install.adoc[Install Flex Gateway] and xref:gateway::flex
 
 . Click *Next*.
 +
-include::partial$task-configure-proxy.adoc[tags=mid-steps;asset-type-options]
+include::partial$task-configure-proxy.adoc[tags=mid-steps;asset-type-options-flex]
 
 . Configure the downstream configuration settings:
 +