[FEATURE REQ] - APIs assignation to products

[paulaingenia]

Please describe the feature.

Hi!

I was checking the files generated by extractor pipelines and for APIs assigned to products the files is inside folder products, "products" has folders for each product and inside each folder there is a file apis.json who contains the APIs assigned for such product, example /products/users/apis.json. For cases where we have mutiple teams working on the same APIM we have multiples repositories for APIs and I think is better to have an approach similar to "tags" where de assignation is in the "apis" folder, example: apis/users/tags.json in the same way we could have apis/users/products.json.

Thanks in advance!

[waelkdouh]

@guythetechie in our next release we are working on modifying the behavior of the extractor to match what @paulaingenia is requesting here correct?

[paulaingenia]

Hi guys!

Do you have an update about this topic?

Thanks in advance!

[waelkdouh]

@paulaingenia as you are probably aware this is an open source project on top of our daily jobs. So we can't promise any timelines. Having said that we are actively working on this project and we try to tackle issues when we can. We will respond here when a resolution has been reached here. So please avoid reaching out for progress updates.

[guythetechie]

@paulaingenia - APIM does the product-API assignment at the product level, not the API level. We're trying to keep our API consistent with it to make updates easy. That said, we're tweaking the product-API level as proposed here. Things will still be in the products folder, but our update should make conflicts across teams less likely.

[paulaingenia]

Hi guys! thanks for the answer. I think is a better approach manage products like "tags", but the idea you showed me here improve a little current situation.

Thanks again for your time!