Azure / Azure/apiops

[BUG] Properties are randomly overwritten/empty when moving between environments.

Abierto
#642 4 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
C#
Estrellas
448
Forks
247
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Release version

APIOps v6 (v6.0.1 and v6.0.1.1)

### Describe the bug

The "Description" and "Web Service Url" properties of APIs are sometimes incorrectly overwritten/empty when moving between environments.

The environment I tested in consists of 3 APIM instances, Test, PreProd and Prod. What may differ a little from the standard config is that the 3 APIM instances are each in their own subscription.
Since all other properties seem to work, I don't think that should be the cause.

The API's is imported WSDL services with no problem and have all properties correct in APIM test-Environment after the import.

When moving APIs (about 60 pcs) from Test to PreProd, sometimes the properties is overwritten with incorrect values ​​for some APIs. It can be overwritten in both Test and PreProd.
There may be different APIs that are overwritten at different times.

Property "Description" becomes empty, Property "Web Service Url" gets the value for APIM (base url).
This seems to happen a bit randomly, sometimes it works sometimes it doesn't.
Never seen the problem with other properties.

It seems to appear at the Publish step and that it write wrong values to APIM Test or/and APIM Preprod.
I normally use "publish-artifacts-in-last-commit", but I see that it also could appear when using "Publish-All-Artifact-in-repo".

Also tested version 5 of APIOps but there I don't experience the same problem.

### Expected behavior

That the properties are the same as those in the repo and are not overwritten.

### Actual behavior

See description

### Reproduction Steps

See description. Hard to make a reproduction step. Properties are overwritten randomly at the publish step (I guess)

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comience con el paso de publicación, comparando el comportamiento de "publish-artifacts-in-last-commit" y "Publish-All-Artifact-in-repo" en las instancias de APIM de Test y PreProd. Rastree cómo se gestionan durante la publicación los valores del repo para Description y Web Service Url; se considera terminado cuando esos valores permanecen sin cambios en cada entorno de destino. Actualmente, la reproducción se describe como aleatoria y difícil.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
azure, csharp
Área
api, cloud, devops
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.