DeployBoard / DeployBoard/deployboard-python

[BUG] Deploying to new environment overwrites existing service environment

Open
#145 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
10
Forks
1
PR merge metrics
No merged PRs in 30d

Description

**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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.