[Question] publish-all-artifacts-in-repo option doesn't revert custom policy to default

[kodoktroll]

Release version

v.6.0.1.4

Question Details

Hi, so I was trying out publisher/extractor and I was wondering if retaining the old custom policies in APIM after deleting the custom policy in artifact and running the publisher with publish-all-artifacts-in-repo option is the intended behavior. Because I want to make running publish-all-artifacts-in-repo replace the all the current APIM state to the artifact that was extracted in that particular commit. That means if I delete a custom policy for an arbitrary API via artifact, I want that particular API to use a default policy after I publish using publish-all-artifacts-in-repo. So, I want a solution that perhaps could replicate this kind of behavior, which would be useful for restoring everything in the artifact to APIM.

Expected behavior

Running publisher using publish-all-artifacts-in-repo after deleting policy on an API should make the policy of that API default policy.

Actual behavior

Running publisher using publish-all-artifacts-in-repo after deleting policy on an API doesn't change the old API in APIM.

Reproduction Steps

• Make an API collection and create an API in that collection
• Add a custom policy for that API and save
• Run extractor with extract all option to create an artifact
• Delete the custom policy in that artifact, then commit and push
• Run publisher with publish-all-artifacts-in-repo option
• After publisher is done running, check the result in APIM. Custom policy would still be there.

[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.

[kodoktroll]

Bump