[Question] publish-all-artifacts-in-repo option doesn't revert custom policy to default
- Lenguaje dominante
- C#
- Estrellas
- 448
- Forks
- 247
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### 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.
Guía de contribución
Línea de trabajo
Comienza rastreando cómo gestiona el publisher la opción publish-all-artifacts-in-repo y cómo representa el artefacto del extractor una policy personalizada eliminada. Reproduce el flujo de trabajo de APIM indicado y, después, verifica que publicar el artefacto cambia la API a su policy predeterminada en lugar de conservar la antigua policy personalizada.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- azure, csharp
- Área
- api, cloud
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100