anotherRedbeard

@guythetechie - I tried that branch and still get an error. It is different than the last error and it seems to indicate it's trying to delete the rev=2 api...

@guythetechie I did try this using the Management REST api using just the OpenApi spec `"format":"openapi"` and got the same result so there might not be anything APIOps can do...

Hi @guythetechie , I'm seeing this issue in the first scenario. In the PR that I created #280 I only applied the fix in that one situation as well.

A workaround for now would be to make sure you add the apiinformation.json file to each commit when you change the specification.yaml file and then it will update correctly.

@waelkdouh and @guythetechie I created a new PR that doesn't modify the common/http.cs class for your review. #372 .

@Ronbabious, yes, the suggested workaround should still be used for now. This is in my backlog to create another PR I just haven't had a chance to complete yet.

I have found that you can work around this issue by providing an over-ride in the configuration..yaml file that points the `identityClientId` to the display name of the Named Value...

> @anotherRedbeard ifnuiir issue is resolved please close the issue. Hi @waelkdouh, I don't think it's technically resolved as it should would without you having to add something in the...

One workaound for this is to create a new version set using the [API](https://learn.microsoft.com/en-us/rest/api/apimanagement/api-version-set/create-or-update?view=rest-apimanagement-2022-08-01&tabs=HTTP) with the same id that is saved in your artifacts folder under the `version sets` folder.

@waelkdouh and @guythetechie for this one it looks like it runs the DELETE on the correct revision, but then you can see another DELETE call on the main api. One...