Skip to content

API tagDescriptions are extracted with hardcoded source APIM resource IDs. #307

Description

@erojolopez

Command that triggered the bug

apiops extract

Expected behavior

  • task: AzureCLI@2
    displayName: Run APIOps Extract
    inputs:
    azureSubscription: "$(SERVICE_CONNECTION_NAME)"
    scriptType: bash
    scriptLocation: inlineScript
    inlineScript: |

        SUBSCRIPTION_ID=$(az account show --query id -o tsv)
    
        echo "Using subscription: $SUBSCRIPTION_ID"
    
        apiops extract \
          --subscription-id "$SUBSCRIPTION_ID" \
          --resource-group "${{ parameters.RESOURCE_GROUP_NAME }}" \
          --service-name "${{ parameters.APIM_INSTANCE_NAME }}" \
          --output "$(Build.ArtifactStagingDirectory)/apim-artifacts" \
          --filter filter.yaml
    

apis:

  • apiName:
    diagnostics:
    • '*'
      operations:
    • '*'
      schemas:
    • '*'
      tagDescriptions: []

Actual behavior

API tagDescriptions are extracted with hardcoded source APIM resource IDs.
They cannot be filtered via filter.yaml.
They are not rewritten during environment promotion.
They fail deployment to target APIM instances.

these files get extracted
/apim-artifacts/apis/{api-name}/tagDescriptions/{tag-name}/tagDescriptionInformation.json

apiops CLI version

1.0.4

Environment details

node 22.23.3 x64

CI/CD environment

Azure DevOps

Is this bug blocking you?

Yes

Activity

  1. Christian-Kruse-Quibiq commented on Oct 2, 2026

    @Christian-Kruse-Quibiq

    Same is happening to me

  2. JProvAnt commented on Oct 6, 2026

    @JProvAnt

    I am encountering the same issue when deploying from one environment to the other since the tag descriptions have been extracted and saved with the full ARM path hardcoded.

  3. added
    staleNo activity for 30+ days — will be closed if no further activity
    on Nov 6, 2026
  4. github-actions commented on Nov 6, 2026

    @github-actions

    ⚠️ Stale issue notice — This issue has had no activity for 30 day(s).

    It will be automatically closed after 60 days of inactivity.

    To keep this issue open:

    • Leave a comment describing the current status, or
    • Remove the stale label.

    This notice was posted automatically by the stale issue workflow.

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

    staleNo activity for 30+ days — will be closed if no further activitytype:bugSomething broken

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions