You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/_partials/task-add-api-instance.adoc
+5-12Lines changed: 5 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,9 +99,8 @@ See xref:runtime-fabric::proxy-deploy-runtime-fabric.adoc[Deploying API Proxies
99
99
[arabic]
100
100
.. Click the API from the list under **Select API**. You can search for a specific API if needed.
101
101
.. Update the *Asset type*, *API version*, and *Asset version* if needed.
102
-
.. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. However, you must fix some conformance issues, such as applying policies, after deploying the API instance.
103
-
+
104
-
After deploying the API, view the *Governance Report* to fix conformance issues. For more information about governing API instances, see xref:govern-api-instances.adoc[].
102
+
.. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
103
+
105
104
* Click **Create new API**:
106
105
[arabic]
107
106
.. Enter a *Name* for the new API asset.
@@ -117,9 +116,7 @@ Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are
117
116
****HTTP API:** Select this option if you do not have an API definition file you want to include for your asset.
118
117
119
118
.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
120
-
.. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. However, you must fix some conformance issues, such as applying policies, after deploying the API instance.
121
-
+
122
-
After deploying the API, view the *Governance Report* to fix conformance issues. For more information about governing API instances, see xref:govern-api-instances.adoc[].
119
+
.. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
123
120
. Click *Next*.
124
121
//end::asset-type-options-flex[]
125
122
@@ -137,9 +134,7 @@ Upload a WSDL file for your SOAP API or add the link to the file. +
137
134
This option is not available for Flex Gateway runtime at this time.
138
135
139
136
.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
140
-
.. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. However, you must fix some conformance issues, such as applying policies, after deploying the API instance.
141
-
+
142
-
After deploying the API, view the *Governance Report* to fix conformance issues. For more information about governing API instances, see xref:govern-api-instances.adoc[].
137
+
.. If you chose a *RAML/OAS* asset type, view the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[].
143
138
. Click *Next*.
144
139
//end::asset-type-options[]
145
140
@@ -151,9 +146,7 @@ After deploying the API, view the *Governance Report* to fix conformance issues.
151
146
NOTE: Anypoint API Manager supports OpenAPI Specification (OAS) 3.0, with the exception of the callback feature. To work around this issue, handle the callback outside of the Mule runtime engine domain or use an OAS 3.0 specification that does not use callbacks.
152
147
153
148
.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
154
-
.. View the *Conformance Status* of the API to ensure the API is conformant. However, you must fix some conformance issues, such as applying policies, after deploying the API instance.
155
-
+
156
-
After deploying the API, view the *Governance Report* to fix conformance issues. For more information about governing API instances, see xref:govern-api-instances.adoc[].
149
+
.. View the *Conformance Status* of the API to ensure the API is conformant. If the *Conformance Status* is non-conformant, after deployment, view the *Governance Report* to find and fix the conformance issues. For more information about the *Governance Report*, see xref:govern-api-instances.adoc[]
0 commit comments