Skip to content

API Center: Inconsistent Title Length Validation Between APIM Sync and APIOps CLI #326

Open

Description

@nithinjamespallicka

Question

I noticed an inconsistency between Azure API Center's native APIM synchronization and APIOps CLI publishing.

When APIs are synchronized from Azure API Management to Azure API Center using the native integration, APIs with titles exceeding 50 characters are successfully registered.

However, when extracting the same APIs from API Center using APIOps CLI and attempting to publish them back, publishing fails with a validation error indicating that the title cannot exceed 50 characters.

I have a few questions:

  • Why does native APIM-to-API Center synchronization allow API titles exceeding 50 characters while APIOps CLI publishing does not?

  • Is the 50-character restriction an intentional API Center limitation, or is this an inconsistency between the two integration methods?

  • Is there a plan to align this behavior so that APIs synchronized through the native integration can be extracted and republished without modification?

This creates a challenge when managing API Center resources through GitOps, as APIs successfully synchronized from APIM cannot be republished without modifying their titles.

Context

Steps to reproduce

  • Create an API in Azure API Management with a display name exceeding 50 characters.

  • Synchronize the API to Azure API Center using native APIM integration.

  • Confirm that the API is successfully registered in API Center.

  • Extract the API Center configuration using APIOps CLI.

  • Attempt to publish the extracted configuration back to API Center.

  • Observe the title length validation error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:questionQuestions about usage or behavior

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions