How to account for component dependencies and strict ordering in self-service deployments
Problem Statement
In a fully self-service deployment model, how do we account for cross-component dependencies and cases where a component needs to be deployed as part of a order of components (for example, Gitaly/Praefect getting deployed before any other component)? Where do we capture that information and where do the responsibilities for keeping that information current and correct land?
Potential Implementations
Do we build our self-serve template with a way for component teams to define their own dependency chains/release order, or do we pull that information from a central source, such as the service-catalog
? Are there features of GitLab that exist today that would be of particular use here?
Edited by Matt Field