Azure / Azure/apiops

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

オープン
#642 コメント 4 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
C#
スター
448
フォーク
247
PR マージ指標
30日以内にマージされた PR はありません

説明

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

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

公開ステップから始め、Test と PreProd の APIM インスタンス間で "publish-artifacts-in-last-commit" と "Publish-All-Artifact-in-repo" の動作を比較します。公開中に Description と Web Service Url の repo 値がどのように扱われるかを追跡します。完了の条件は、それらの値がすべての対象環境で変更されないことです。現在、再現はランダムで困難だと説明されています。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
azure, csharp
領域
api, cloud, devops
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
25/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。