Azure / Azure/apiops

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

Aperta
#775 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
C#
Stelle
448
Fork
247
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia tracciando la gestione da parte del publisher dell'opzione publish-all-artifacts-in-repo e il modo in cui l'artefatto dell'extractor rappresenta una policy personalizzata eliminata. Riproduci il workflow APIM indicato, quindi verifica che la pubblicazione dell'artefatto modifichi l'API impostandone la policy predefinita invece di mantenere la vecchia policy personalizzata.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
azure, csharp
Ambito
api, cloud
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
35/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.