This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 33%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EI%3C/text%3E%3C/svg%3E)
I have been attempting to have APIM import our API which resides on Azure Container Apps service. The Container App service has an open API specification on the endpoint /openapi but when the API is imported to APIM the operations are not being created as expected. The operations have been wildcarded rather than created based on the specification.
I would like to have it automatically, rather than change it every time manually.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 10%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
IlicMarko Thanks for posting your question in Microsoft Q&A. Can you share more info about the difference after import vs Open API specification. Is it possible to share the OpenAPI specification?
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
When I import Container App APIM generates wildcard operations instead of Open API Specification which is already included in Container App. Open API specification is as follows:
{"openapi":"3.0.1","info":{"title":"Custom API title","version":"3.14"},"servers":[{"url":"https://calculatorswagger.ambitioussand-d37b45d1.westeurope.azurecontainerapps.io","description":"Generated server url"}],"paths":{"/calculateCashLoan":{"post":{"tags":["financial-controler"],"operationId":"getTestData","requestBody":{"content":{"application/json":{"schema":{"type":"string"}}},"required":true},"responses":{"200":{"description":"OK","content":{"*/*":{"schema":{"type":"string"}}}}}}}},"components":{}}
IlicMarko thanks for sharing the Open API spec. I imported the API using this spec and found it generated only one POST operation for getTestData as described in the spec (see screenshot below:).
If you are able to reproduce this issue, we might need to review your APIM instance and investigate the backend logs. Please send an email to azcommunity@microsoft.com referencing this thread with your subscription ID (not name), details and subject as "Attn: Muthu". I will assist you with next steps.
IlicMarko Thanks for sharing the additional details.
Update for the community:
Initially, the container app was imported in APIM via Open API Spec as .yaml file and it generated wild card operations (doc reference: OpenAPI specification versus wildcard operations). IlicMarko resolved the issue by changing the spec to .json and worked perfectly.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more