Support for parameterised configurations in .gitpod.yml
#8252
Labels
enhancement
feature: gitpod yml
All things related to the gitpod.yml
feature: mono/meta repo
feature: prebuilds
meta: never-stale
This issue can never become stale
Current Approach
Currently, the way that gitpod works is via one single declarative syntax for a project set up, but, this approach doesn't work well for scenarios where you have (potentially) many different permutations of a given project or setup (e.g. mono-repo's or more advanced projects). Currently, the best way of doing this is via URL parameters or via environment variables that alter the project configuration, in combination with custom scripts and/or a makefile.
Proposal
Allow a given project to specify a number of input parameters (type definitions and optionality) for a project configuration. This feature would then allow the creation of any number of different permutations of a given project (e.g. a matrix), and a project or workspace. Each permutation of the matrix is then treated as it's own "project" configuration e.g. it has it's own pre-build and allows custom start tasks to be configured. A good real example of this is the DrupalPod project, which uses a Chrome extension to specify input parameters, that are passed via URL, and then consumed in scripts to create different set-ups of the project.
Examples
Example of this within DrupalPod, which uses a browser extension form [1].
Similar feature in other products
The text was updated successfully, but these errors were encountered: