Skip to content

[Question] After updating to latest version publisher start failing with errors #849

Closed

Description

@nepsmaddy

Release version

7.0.1

Question Details

When we run publisher before, it will automatically deploy the artifacts which are extracted in artifacts. Now it is failing for random error, for propertyid and subscription to be set. Please find below error snapshot.

System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/***/resourceGroups/grd-uat-eus2-gapi-rg/providers/Microsoft.ApiManagement/service/grd-uat-eus2-gapi-apim-01/workspaces/WS-POC/tags/ws/apiLinks/69fa265f0182f50a2066ef1b?api-version=2024-05-01 failed with status code 400. Content is '{"error":{"code":"LinkedInvalidPropertyId","message":"Property id '/workspaces/WS-POC/apis/ws-api-v1' at path 'properties.apiId' is invalid. Expect fully qualified resource Id that start with '/subscriptions/{subscriptionId}' or '/providers/{resourceProviderNamespace}/'."}}'.

Expected behavior

It should publish to new instance without changing anything in the configs.

Actual behavior

It is failing required saying need to put fully qualified resource id.

I am not sure if i am missing some configuration as per new version requirement

Reproduction Steps

  1. Run extractor and generate artifacts
  2. Run publisher

Activity

  1. github-actions commented on May 7, 2026

    @github-actions
      Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
      Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.
    
  2. guythetechie commented on May 8, 2026

    @guythetechie
    Contributor

    Investigating.

  3. added a commit that references this issue on May 8, 2026
  4. guythetechie commented on May 8, 2026

    @guythetechie
    Contributor

    Fixed, please use the latest release. You'll have to extract the resources again first before publishing them.

  5. nepsmaddy commented on May 8, 2026

    @nepsmaddy
    ContributorAuthor

    Thank you this issue is resolved now but now the another issue is happening.. Not sure how to give relative resource ids.

    crit: apiops.publisher[0] Publisher failed. Please check the logs for more details. System.InvalidOperationException: Found at least one validation error: Resource 'workspaces/WS-POC/tags/ws/apiLinks/69fa265f0182f50a2066ef1b' is missing its predecessor 'workspaces/WS-POC/apis/ws-api-v1'. Resource 'workspaces/WS-POC/products/ws-product/apiLinks/69fa265f6b43546dbe2f469a' is missing its predecessor 'workspaces/WS-POC/apis/ws-api-v1'.

    is there any examples we can follow how to point this.

  6. guythetechie commented on May 8, 2026

    @guythetechie
    Contributor

    Did you rerun the extractor? The publisher is saying that it can't find the API ws-api-v1 in workspace WS-POC, even though tag ws and product ws-product refer to it.

  7. guythetechie commented on May 20, 2026

    @guythetechie
    Contributor

    Closing, please reopen the issue if needed.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions