Is your feature request related to a problem? Please describe
I would love the ability to add some extra enhancements to the "up and running" state of a DrupalPod instance. For example, when I'm using DrupalPod to develop my contrib module, there are some other modules I like to have to help me. I might be writing an add-on for Commerce, so I might want Commerce to come pre-installed or available in the repo, at it's latest -dev or stable verrsion.
Describe the solution you'd like
Support reading a contrib project's "drupalpod.yaml" file to provide some of the extra configuration.
Describe alternatives you've considered
I thought, well, I could just fork DrupalPod and make my own with my own scripts, but this seems like a useful feature to many module developers and contributors across the board -- being able to give contributors a known good "starting point" simplifies so much more of the process.
Is your feature request related to a problem? Please describe
I would love the ability to add some extra enhancements to the "up and running" state of a DrupalPod instance. For example, when I'm using DrupalPod to develop my contrib module, there are some other modules I like to have to help me. I might be writing an add-on for Commerce, so I might want Commerce to come pre-installed or available in the repo, at it's latest -dev or stable verrsion.
Describe the solution you'd like
Support reading a contrib project's "drupalpod.yaml" file to provide some of the extra configuration.
Describe alternatives you've considered
I thought, well, I could just fork DrupalPod and make my own with my own scripts, but this seems like a useful feature to many module developers and contributors across the board -- being able to give contributors a known good "starting point" simplifies so much more of the process.
Additional context
https://drupal.slack.com/archives/C01N7HQSSFN/p1684339120557419