guythetechie

@rohit3d2003 - thanks, I was able to reproduce the behavior. Looks like the APIM REST API sets things to the base URL if you don't explicitly pass a ``null`` service...

It unfortunately looks like this behavior is by design in APIM. Our tool just provides an abstraction layer over the APIM REST APIs. We won't try to change their behavior....

Will investigate. We might be reading `serviceUrl: null` as `serviceUrl: "null"` in configuration.

Can you share the policy file under `/artifacts/apis/wyhq-nileplus-d-nifiserverlog/operations/When_a_HTTP_request_is_received-invoke/policy.xml`?

@PeiyuKuo - I don't see anything attached. Don't know if Github uploads attachments to the issue when you respond by email. Can you try uploading your file?

Thanks, @Banchio. The proposal makes sense. Please wait until our next RC release with support for workspaces though (should be sometime next week). Don't want you to make changes while...

@Banchio - code has been merged to main, please feel free to start working on this. The code base has changed significantly since your last PR, so don't hesitate to...

Looks great, thanks! The publisher will be impacted as well; it expects a format in the policy `PUT` request. We currently hardcode it here for example: https://github.com/Azure/apiops/blob/bf5cc1234a44c3221b60afa6dda245aab649cb47/tools/code/publisher/ApiPolicy.cs#L148 Since it's needed...

@Banchio - What you have looks great. Here is what I was suggesting, but it's not necessary. For API specifications, we have an `ApiSpecification` type that has several options. We...

API filters only affect items related to specific APIs. Service-level policies sit above APIs and aren't impacted by API filters. Just like product-level policies wouldn't be affected by API filters;...