Azure / api-management-developer-portal

Developer portal provided by the Azure API Management service.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Definition schema not show in operation details

pbychkoviak opened this issue · comments

Bug description

Definition schema not show in operation details

Reproduction steps

  1. Create new API Management service instance
  2. Go to Echo API and create new definition
  3. Assign this new definition to the "Create resource" operation
  4. Open developer portal, select "Create resource" operation and see that the definition schema is empty

Expected behavior

Definition schema is show

Is your portal managed or self-hosted?

Managed

Environment

  • Operating system: Windows 11
  • Browser: any browser

Additional context

image
image
image

hello @pbychkoviak , thanks for reaching out!
We have a regression in the current release, that creates some issues when loading APIs' definitions. We have prepared a fix and prioritized the deployment (ETA is this week).
If it is urgent for you, please send your apim instance(s) name(s) to apimportalfeedback@microsoft.com, so we can roll them back.
Apologies for the inconveniences and thank you for udnerstanding!

Now it works. Thanks.

The fix was deployed in all stages.

@malincrist we had the same issue across different environments. It seems that your deployed fix have solved it not showing the fields. Which is great, thanks. We also use a managed developer portal.

However, now we are experiencing that when changing the API from the dropdown menu, it does not change the descriptive texts in request body for OpenAPI definitions which have the same 'definition names' the description text remains the same from the previous API.
When changing the API using the dropdown list (1) from SP v2 to TC V2, I will still have the descriptive text of SP v2 in the main window
image

@pbychkoviak are you experiencing similar behavior in your environment?

@MBVDK no, I do not observe what you described.

hi @MBVDK , thank you for reporting this new issue with definitions!
We identified the issue and fixed it. It will be shipped with the next release (ETA 1-2 weeks). In the meantime, as a workaround, you can clear the cache and the correct definitions will be loaded. Apologies for the inconveniences!