Azure / Azure/apiops

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

Offen
#642 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
C#
Sterne
448
Forks
247
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Beginnen Sie mit dem Veröffentlichungsschritt und vergleichen Sie das Verhalten von "publish-artifacts-in-last-commit" und "Publish-All-Artifact-in-repo" in den Test- und PreProd-APIM-Instanzen. Verfolgen Sie, wie die Repo-Werte für Description und Web Service Url während der Veröffentlichung behandelt werden; abgeschlossen ist die Aufgabe, wenn diese Werte in jeder Zielumgebung unverändert bleiben. Die Reproduktion wird derzeit als zufällig und schwierig beschrieben.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
azure, csharp
Bereich
api, cloud, devops
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.