Merge pull request #494 from mulesoft/W-12222307-add-flex-tls

W 12222307 add flex tls

Author: glenn-rodgers-sf

modules/ROOT/pages/_partials/task-configure-proxy.adoc

@@ -147,6 +147,10 @@ If you upload an OAS API specification to an API proxy version 1.0 or earlier, y
 . If you plan to have xref:building-https-proxy.adoc[HTTPS] communications, specify a TLS Context.
 . Click *Next*.
 //end::tls[]
+//tag::configure-endpoint[]
+. xref:api-manager::configure-api-task.adoc[Configure the endpoint].
+. Click *Next*.
+//end::configure-endpoint[]
 //tag::last-steps-heading[]
 
 [[review_save_and_deploy]]

modules/ROOT/pages/configure-api-task.adoc

@@ -14,11 +14,13 @@ Not all options are available depending on the runtime as well as the API.
 | *API instance label* | Specifies a label for the API. | No | If you have multiple managed instances of the same API, add a label to differentiate each instance from the others.
 | *Implementation URI* | The URL to access for the proxy or the API. It must end with a /. | Yes|  For example, you can use the URL of your API asset in Exchange. 
 | *Consumer endpoint* | Specifies a proxy application's address for consumers to use for sending requests.| No |
-| *Proxy version* | Specifies the version of the proxy to use for the endpoint.| No |
 | *Base path* | Specifies the URL prefix for all API paths, relative to the host root. It must start with a leading slash /. | No | 
-| **Advanced Options** |  |  |
 | *Scheme* | Specifies whether to use HTTP or HTTPS. | Yes | If you select HTTPS, specify a TLS context for inbound traffic.
+| *TLS Context for inbound traffic* | Specifies the TLS Context used for the inbound traffic of HTTPS APIs. | No | xref:gateway::flex-conn-tls-config.adoc[Configure a TLS Context for Flex Gateway] before adding a TLS Context to your API.
 | *Port* | Specifies the number to use if the displayed port is incorrect. | No | Port can be shared between API instances over the same Target as long as the Base paths are different. Only available on Flex 1.2.0+.
+| *Client provider* | Specifies a client provider for the API. | No | Anypoint Platform acts as the client provider by default. To configure an external client provider, see xref:access-management::managing-api-clients.adoc[Client Providers]. 
+| **Advanced Options** |  |  |
+| *TLS Context for outbound traffic* | Specifies the TLS Context used for the outbound traffic. | No | xref:gateway::flex-conn-tls-config.adoc[Configure a TLS Context for Flex Gateway] before adding a TLS Context to your API.
 |===
 
 == Configure an API Instance on Service Mesh Options

modules/ROOT/pages/create-instance-task.adoc

@@ -14,17 +14,17 @@ the sandbox environment, and you want to promote it to the current or production
 * *Import API from zip file:* Select this option if you have exported an API Instance from a different Anypoint Platform
 instance.
 
-When you are promoting or importing an API Instance, you will not have options to alter the configuration. However,
-when you add a new API Instance, you will need to configure the endpoint as well as other settings.
+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 xref:configure-api-task.adoc[configure the endpoint] as well as other settings.
 
 == Add a New API
 
 . Log in to Anypoint Platform.
 . In the navigation bar or the Anypoint Platform page, click *API Manager*.
 . Click *Add API* and select *Add new API*.
 . Select and configure your runtime from the following options:
-Flex Gateway:: Select Flex Gateway for any APIs that need a flexible, performant API gateway
-that will work with distributed and microservices environments and fit into your CI/CD environments.
+Flex Gateway:: Select Flex Gateway for any APIs that need a flexible and performant API gateway
+that works with distributed and microservices environments and fits into your CI/CD environments.
 +
 Choose the connected Flex Gateway you have installed and registered from the list under *Select a gateway*.
 +
@@ -52,11 +52,11 @@ include::partial$task-configure-proxy.adoc[tags=target-type-bullet;target-type]
 Service Mesh:: Select Service Mesh to extend Anypoint Platform API Management capabilities to your
 Istio service mesh through the deployment of a Mule Adapter.
 +
-NOTE: After adding the API on Anypoint Platform, you will need to bind it to a service using the Anypoint Service Mesh client. See xref:service-mesh::configure-service-mesh.adoc#methods-for-configuring-anypoint-service-mesh[Methods for Configuring Anypoint Service Mesh] for more information.
+NOTE: After adding the API on Anypoint Platform, you need to bind it to a service using the Anypoint Service Mesh client. See xref:service-mesh::configure-service-mesh.adoc#methods-for-configuring-anypoint-service-mesh[Methods for Configuring Anypoint Service Mesh] for more information.
 +
 . Click *Next*.
 +
-include::partial$task-configure-proxy.adoc[tags=mid-steps;asset-type-options;last-steps,leveloffset=+2]
+include::partial$task-configure-proxy.adoc[tags=mid-steps;asset-type-options;configure-endpoint;last-steps,leveloffset=+2]
 
 
 == Promote API from Environment