digitalocean / digitalocean/doctl

Ability to deploy separate parts of an App

Open
#1,461 0 comments 1 reaction 0 assignees View on GitHub
suggestion
Dominant language
Go
Stars
3.4k
Forks
496
Avg merge
1d 2h
Merged PRs (30d)
31

Description

**What is the problem this feature would solve? Please describe.**
I have an App which consists of a static site, a backend api & a database. Whenever I create a new deployment for this app it seems like it's redeploying everything. The api deployment is controlled through GitHub actions and is not connected with my GitHub repository. I want to make sure the exact same docker image that I have tested in dev is the one I later deploy to production. My static site is connected to my GitHub repository because you offer no other way to do it. And for me to control the deployment of that I see no other way to disable `AutoDeploy` and run `doctl apps create-deployment` for it to fetch the latest code from my repo and deploy it. I don't like this approach though since deploying based on a commit hash can result in different artifacts, because of dependencies of my project, but it seems like the only way.

**Describe the solution you'd like**
I would like to be able to instruct `doctl apps create-deployment` to only deploy a specific component of my App, for example the static_site. I would also like a way to deploy an artifact to my static site rather than DO creating an artifact for me based on a snapshot of my code.

**Additional context**
Again, the issue with creating a new artifact for each deployment based on a snapshot of code is that it can result in different artifacts because of dependencies.

BR

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.