question

JeanRojas-2530 avatar image
0 Votes"
JeanRojas-2530 asked ·

Is there any workaround to use custom x- based extensions?

Im trying to import my openAPI v3 specification to api management service, but the import fails due invalid references, digging into the problem I found an article about openapi restrictions, I managed to solve uniqueIds problem but Im stuck with x- based extensions restrictions; I mean, I can copy the literal refer object into the field which references, but my api definition is really huge and is easier to our team to keep definitions outside the schema property for maintainability, so I would like to know if there is any workaround to reference external extensions under my components.

I attached a picture about what Im trying to achieve
9055-screenshot-from-2020-06-03-13-29-39.png


azure-api-management
· 1
10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @JeanRojas-2530 - We are now actively investigating and will answer with our findings soon.

0 Votes 0 ·

1 Answer

MayankBargali-MSFT avatar image
0 Votes"
MayankBargali-MSFT answered ·

Hi @JeanRojas-2530


This is the import limitation and no workaround: https://docs.microsoft.com/en-us/azure/api-management/api-management-api-import-restrictions a


x-ms-paths and x-servers are the only supported extensions.

Recursion - API Management doesn't support definitions defined recursively (for example, schemas referring to themselves).



· 1
10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @JeanRojas-2530


Following up on my previous comment. Please let me know if you have any queries or concerns.



0 Votes 0 ·