DeployBoard / DeployBoard/deployboard-python

[BUG] Deploying to new environment overwrites existing service environment

未關閉
#145 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
bug
主要語言
Python
星號
10
分支
1
PR 合併指標
30 天內沒有已合併 PR

描述

**Describe the bug**
When you deploy a service/application to Dev (for example) it will work fine. it will create the new application, and create the environment.

When you attempt to deploy that same service/application to Prod it will work fine, but I believe it is completely overwriting the object in the services collection, so it essentially deletes the Dev environment, and we now only see the Prod environment.

This is only within the scope of the service in the services collection, both environments will exist in the environments collection as expected.

**To Reproduce**
Steps to reproduce the behavior:
1. Deploy to dev.
2. Go to the Dashboard page, observe it is there as expected.
3. Deploy same app to prod.
4. Go back to the Dashboard page, observe Dev is gone, and only Prod is there.

**Expected behavior**
Deploying to an existing Service, should only add a new environment, or update the existing environment. it should not overwrite the entire environments field.

**Screenshots**
none

**System Information (please complete the following information):**
- API

**Additional context**
None

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

首先追蹤寫入服務記錄的 API 部署流程,並比較對 services 和 environments 集合的更新。將同一個應用程式先部署到 Dev,再部署到 Prod,以重現此問題,然後檢查已儲存的服務資料和 Dashboard 結果。當兩個環境都維持可見,且仍可更新現有環境而不移除其他環境時,即表示完成。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
mongodb, python
領域
api, backend, database
Issue 類型
缺陷
難度
3/5
預估耗時
1-2 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。