Question: API.name populated with full ARM path after v2.33.0 ARM migration - Expected behavior?

[stephanbail]

Context

We're running API Management Developer Portal v2.33.0 in a self-hosted environment with an Application Gateway routing requests to Azure API Management. After migrating from v2.24.0 to v2.33.0, we're encountering issues with API routing.

The Observation

After the ARM migration in v2.33.0, we noticed that the Api model constructor sets this.name to the full ARM resource ID:

// src/models/api.ts line 116
this.id = contract.id;
this.name = contract.id;  // Full ARM path is used as name

Reference:

api-management-developer-portal/src/models/api.ts

Line 116 in c98b19b

this.name = contract.id;

This was changed from the previous version where:

this.name = contract.name;  // Before ARM migration

The Issue We're Experiencing

When api.name contains the full ARM path (e.g., /subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.ApiManagement/service/xxx/apis/test-api), it causes routing problems:

1. API operations fail to load with 404 errors
2. URLs are malformed with double ARM paths like:

   /apis//subscriptions/.../apis/test-api
   

3. Code expecting just the API name fails, for example:

   // This creates an invalid path when apiName is the full ARM path
   await this.apiService.getApi(`apis/${apiName}`);

Our Setup

• Deployment: Self-hosted
• Version: 2.33.0
• Architecture: Application Gateway → Azure API Management
• Configuration: Using MapiClient with custom routing through Application Gateway

Questions

1. Is this the expected behavior after the ARM migration? Should api.name contain the full ARM path or just the API identifier?

2. How should the contract.id be processed? Should we extract just the API name from the ARM path, or is there a different field we should use?

3. Is there a configuration setting we're missing that would handle this correctly?

4. For self-hosted deployments, are there special considerations for how the API data should be structured?

What We've Tried

• Verified our Application Gateway passes through responses unchanged
• Checked that our MapiClient correctly routes to the ARM endpoints
• Confirmed the API list loads successfully, but routing to individual APIs fails

Possible Solution?

Should the code extract just the API name from the ARM path, like:

this.name = Utils.getResourceName("apis", contract.id);