[Question] publish-all-artifacts-in-repo option doesn't revert custom policy to default
- Vorherrschende Sprache
- C#
- Sterne
- 448
- Forks
- 247
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### 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.
Beitragsleitfaden
Rechercherichtung
Beginne damit, die Behandlung der Option publish-all-artifacts-in-repo durch den Publisher nachzuverfolgen und zu untersuchen, wie das Extractor-Artefakt eine gelöschte benutzerdefinierte Policy darstellt. Reproduziere den aufgeführten APIM-Workflow und überprüfe anschließend, dass das Veröffentlichen des Artefakts die API auf ihre Standard-Policy ändert, anstatt die alte benutzerdefinierte Policy beizubehalten.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- azure, csharp
- Bereich
- api, cloud
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100