Use service a dependency system instead of deployment stages

Open
#49 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
devops

Research direction

This is a roadmap-level proposal with no repository files, tests, or entry points identified. Review the linked Featurebase and Jira records first, then map the existing stages system before defining dependency-based deployment behavior and its completion criteria.

Written by the indexing model from the issue text.

Description

status: later

We will move out from the stages system and instead use a dependency system to define the deployment pipeline.

For example:

you will be able to define that :

  • a service A depends on the service B

  • a service C depends on nothing

  • a service D depends on B and C

Qovery will automatically execute the deployments based on these dependency and you won’t have to define stages anymore.

Votes: 1 | Submitted: 2025-01-20 | Featurebase: https://roadmap.qovery.com/p/use-service-a-dependency-system-instead-of-deployment-stages | Author: Alessandro Carrano | Jira: https://qovery.atlassian.net/browse/QOV-678

Dominant language
No language data
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Qovery/Roadmap

All issues in Qovery/Roadmap

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.