Azure / Azure/apiops

[BUG] Product not being associated with API after publishing

Open
#695 11 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
448
Forks
247
PR merge metrics
No merged PRs in 30d

Description

### Release version

6.0.1

### Describe the bug

When publishing an API (with the setting "publish-all-artifacts-in-repo") the product is not being associated with the API. The product itself is being published, but it is not being connected with the API. In previous APIOps versions this worked fine. Since upgrading to version 6.0.1 this has stopped working for us.

Artifacts:

![Image](https://github.com/user-attachments/assets/d5f4a256-1fdf-4644-9bc5-02cf573f2de9)

In the older version of the APIOps the extractor would associate the product with the api using the apis.json file (this is a screenshot from version v5.1.1 of APIOps):

![Image](https://github.com/user-attachments/assets/97fb4ea3-e8b0-48df-b625-db2375cd4ff9)

This worked as expected, the product was associated with the API and when publishing, the product was connected with the API in the portal.

### Expected behavior

When running the publisher, the product should be associated with the API.
In the portal, product association can be verified:
![Image](https://github.com/user-attachments/assets/bbad9c00-eaa9-4ab7-b612-101b35fe2fd1)

### Actual behavior

No product is being associated with the API either in the artifacts or in the portal.
In the portal no product is associated with the API:
![Image](https://github.com/user-attachments/assets/7ae3708f-6685-4b56-8c75-3bd40cd1c68d)

### Reproduction Steps

Using APIOps v6.0.1
Extract API using extractor pipeline, with specific productName defined in extractor config file.
Publish API using publisher pipeline.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.