Skip to content

Commit 08288f4

Browse files
Merge pull request #540 from mulesoft/W-14295864-api-versioning-gr
W-14295864 Add asset version
2 parents 1ff8b7d + fe66bc0 commit 08288f4

2 files changed

Lines changed: 18 additions & 10 deletions

File tree

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

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,9 @@ See xref:runtime-fabric::proxy-deploy-runtime-fabric.adoc[Deploying API Proxies
9898
* Click **Select API from Exchange** if you have an API shared with you through Exchange that you want to manage.
9999
[arabic]
100100
.. Click the API from the list under **Select API**. You can search for a specific API if needed.
101-
.. Update the *Asset type*, *API version*, and *Asset version* if needed.
101+
.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
102+
+
103+
For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
102104
.. 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[].
103105

104106
* Click **Create new API**:
@@ -115,7 +117,9 @@ See xref:runtime-fabric::proxy-deploy-runtime-fabric.adoc[Deploying API Proxies
115117
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.
116118
** **HTTP API:** Select this option if you do not have an API definition file you want to include for your asset.
117119

118-
.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
120+
.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
121+
+
122+
For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
119123
.. 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[].
120124
. Click *Next*.
121125
//end::asset-type-options-flex[]
@@ -133,7 +137,9 @@ Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are
133137
Upload a WSDL file for your SOAP API or add the link to the file. +
134138
This option is not available for Flex Gateway runtime at this time.
135139

136-
.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
140+
.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
141+
+
142+
For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
137143
.. 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[].
138144
. Click *Next*.
139145
//end::asset-type-options[]
@@ -145,7 +151,9 @@ This option is not available for Flex Gateway runtime at this time.
145151
+
146152
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.
147153

148-
.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
154+
.. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
155+
+
156+
For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
149157
.. 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[]
150158
. Click *Next*.
151159
//end::raml-oas[]
@@ -154,7 +162,7 @@ NOTE: Anypoint API Manager supports OpenAPI Specification (OAS) 3.0, with the ex
154162
//tag::soap[]
155163
.. Select **SOAP API** as the **Asset type**.
156164
.. Select either *Upload a WSDL* or *Use an external link* as the method.
157-
.. Optionally, click *Advanced* to edit the *AssetId* and the *Version*.
165+
.. Update the *Asset type*, *API version*, and *Asset version* if needed.
158166
. Click *Next*.
159167
//end::soap[]
160168

modules/ROOT/pages/manage-versions-instances-concept.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,16 +3,16 @@ ifndef::env-site,env-github[]
33
include::_attributes.adoc[]
44
endif::[]
55

6-
In Anypoint Exchange (Exchange), you can add, delete, and deprecate API versions, also known as _Exchange assets_. An API version in Exchange can have its own RAML file, API portal, and URL. For more information on how to manage API versions in Exchange, see xref:exchange::manage-versions.adoc[Manage Versions].
6+
After you publish new version details for an API definition to Exchange, you must update the *Asset version* of your deployed API instances in API Manager to reflect the changes.
77

8-
After you publish new version details for an API definition to Exchange, you must change the version of your API instance in API Manager if you want the instance to reflect the latest version. For more information on API instances, see xref:api-instance-landing-page.adoc[API Instance].
8+
For more information about versions in Exchange, see xref:exchange::asset-versions.adoc[].
99

1010
To change the asset version of an API instance:
1111

12-
. Navigate to *Anypoint Platform* > *API Manager*.
13-
. In *API Administration*, click the name of the API instance whose version you want to manage.
12+
. Navigate to *Anypoint Platform* > *API Manager*.
13+
. In *API Administration*, click the name of the API instance for which you want to change the version.
1414
. Select *Actions* > *Change API specification*.
15-
. In *Asset version*, Select *latest*.
15+
. In *Asset version*, select your desired version.
1616
. Click *Change*.
1717

1818
== See Also

0 commit comments

Comments
 (0)