[APIM - DeveloperServices] 2022-04-01-preview

[azure-sdk]

New API Review meeting has been requested.

Service Name: API Management
Review Created By: Harun Heybet
Review Date: 3/7/2023 1:00 PM PT
PR: #22470
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: here

Description: Developer Services API Preview Release.
https://microsofteur-my.sharepoint.com/:p:/g/personal/harunheybet_microsoft_com/Ebajf5hArddMrxvZv9FUxJcB1Q54ak7pJ25lzMplJ6WcMQ?e=Pl6Kfl

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

[markweitzel]

API Stewardship Review: 7-Mar-23

• There's a mix of v2 & v3 schemas -- we'll need all v2 openapi docs.
• @johanste -- on point to help jumpstart TypeSpec effort
• drop the count property, or if it's supposed to be a total count, name it totalCount
  • we recommend dropping this and using a nextlink or paging approach -- calculating the results can be expensive.
• remove the $ for skip & top
• Do we need both POST and PATCH for user creation?
  • We recommend just using PATCH and removing POST

Next Steps

The team should move to TypeSpec and then we can review the API in its entirety.
Recording

[azure-sdk]

New API Review meeting has been requested.

Service Name: API Management
Review Created By: Harun Heybet
Review Date: 05/17/2023 09:00 AM PT
PR: #23546
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: here

Description:

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

[markweitzel]

API Stewardship Board Review: 17-May-23

Recommendation

• We should not "duplicate" the API surface area based on an implementation, e.g. caching. We should figure out a way to remove the duplication.

• The identities endpoint should be looked at because it is a very confusing path. How it's used is

• Consider using the POST action pattern for /confirmations/users/{userId}/identities/basic. You don't really have a confirmations collection either.