diff --git a/code-builder-home/modules/ROOT/pages/_partials/acb-api-design.adoc b/code-builder-home/modules/ROOT/pages/_partials/acb-api-design.adoc index 753f60945..8233d2595 100644 --- a/code-builder-home/modules/ROOT/pages/_partials/acb-api-design.adoc +++ b/code-builder-home/modules/ROOT/pages/_partials/acb-api-design.adoc @@ -10,6 +10,8 @@ * OAS 3.0 (YAML) * OAS 3.1 (JSON) * OAS 3.1 (YAML) +* OAS 3.2 (JSON) +* OAS 3.2 (YAML) // end::api-spec-versions[] // diff --git a/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc b/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc index 7539ced75..409884f6f 100644 --- a/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc +++ b/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc @@ -171,7 +171,7 @@ To add an API spec fragment to a spec: ** RAML specs: Use the `!include` directive. -- + -For OAS 3.0 and 3.1 APIs, scaffolding supports `$ref` API fragments from Exchange, including fragments with transitive dependencies. OAS 3.1 requires Mule runtime 4.13 or later and APIkit for Mule 4 1.13.2 or later. DataSense resolves types defined in fragment files when you scaffold into a Mule project that uses a supported Mule runtime version (currently Mule 4.9.19, Mule 4.11.6, and Mule 4.13). +For OAS 3.0, 3.1, and 3.2 APIs, scaffolding supports `$ref` API fragments from Exchange, including fragments with transitive dependencies. OAS 3.1 and OAS 3.2 require Mule runtime 4.13 or later and APIkit for Mule 4 1.13.2 or later. DataSense resolves types defined in fragment files when you scaffold into a Mule project that uses a supported Mule runtime version (currently Mule 4.9.19, Mule 4.11.6, and Mule 4.13). + [tabs] ==== diff --git a/code-builder-home/modules/ROOT/pages/des-designing-api-specs.adoc b/code-builder-home/modules/ROOT/pages/des-designing-api-specs.adoc index 80ee0d579..cd814a9d4 100644 --- a/code-builder-home/modules/ROOT/pages/des-designing-api-specs.adoc +++ b/code-builder-home/modules/ROOT/pages/des-designing-api-specs.adoc @@ -22,9 +22,13 @@ Supported OAS and RAML versions are: * OAS 3.0 (YAML) * OAS 3.1 (JSON) * OAS 3.1 (YAML) +* OAS 3.2 (JSON) +* OAS 3.2 (YAML) * RAML 1.0 * RAML 0.8 +NOTE: When you create or edit an OAS 3.2 API specification in JSON or YAML, Anypoint Code Builder validates the specification inline and autocompletes JSON Schema 2020-12 keywords. + Supported AsyncAPI versions are: * AsyncAPI 2.6 (JSON) @@ -39,7 +43,7 @@ Create, include, or reference API fragments within your API specification. Supported API specification languages and syntaxes for API fragments are: -* OAS 3.0 and 3.1 +* OAS 3.0, 3.1, and 3.2 ** YAML ** JSON * RAML 1.0 diff --git a/code-builder-home/modules/ROOT/pages/imp-implement-api-specs.adoc b/code-builder-home/modules/ROOT/pages/imp-implement-api-specs.adoc index 98cbefd32..35854b818 100644 --- a/code-builder-home/modules/ROOT/pages/imp-implement-api-specs.adoc +++ b/code-builder-home/modules/ROOT/pages/imp-implement-api-specs.adoc @@ -30,7 +30,7 @@ the spec to Exchange, see xref:imp-implement-local-apis.adoc[]. //shared implementation prereqs include::partial$acb-reusable-steps.adoc[tags="prereqs-implementation"] -* If your API spec is OAS 3.1, make sure your project uses Mule runtime 4.13 or later and APIkit for Mule 4 1.13.2 or later. +* If your API spec is OAS 3.1 or OAS 3.2, make sure your project uses Mule runtime 4.13 or later and APIkit for Mule 4 1.13.2 or later. [[scaffold-new-integration]] == Scaffold an API into a New Project