My Oracle Support Banner

YAML File Not According To OpenAPI 3.0 Specification And RFC 3986 Standard. Cannot Be Imported. (Doc ID 2981993.1)

Last updated on OCTOBER 20, 2023

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version 23.1 to 23.1 [Release 23.1]
Information in this document applies to any platform.

Symptoms

On : 23.1 version, Merch - Installation

ACTUAL BEHAVIOR
---------------
YAML file not being created according to OpenAPI 3.0 specification and RFC 3986 standard. Cannot be imported into other applications. The header of the file when downloaded shows as openapi: 3.0.1
This issue is seen when the yaml file (available to download from swagger page) is imported into an industry tool, Informatica, used by the customer. That tool is very strict on standard and hence while other industry tools accept the MFCS yaml, it fails in that tool.

EXPECTED BEHAVIOR
-----------------------
The YAML file needs to be OpenAPI 3.0 specification and RFC 3986 standard to be compatible with an industry tool (eg Informatica)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Download the YAML file
2. Import it in any tool that executes OPEN API 3 / RFC 3986 validation
3. File is validation fails

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.