Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to deploy separate parts of an App #1461

Open
razum90 opened this issue Nov 11, 2023 · 0 comments
Open

Ability to deploy separate parts of an App #1461

razum90 opened this issue Nov 11, 2023 · 0 comments

Comments

@razum90
Copy link

razum90 commented Nov 11, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant