Is there an existing issue for this?
Is your feature request related to a problem?
I love the idea of this add-on, bit it makes one fundamental assumption that makes it difficult for me to work with: it assumes that each environment is meant to work with one (and only one) contribution project. On practice, as the maintainer of dozens of contrib projects, I often prefer the opposite. I want to have a single site with lots of different modules pulled in as got repos, and it is immensely useful to have DDEV snapshots that have one or more projects installed with relevant data and settings.
That kind of workflow doesn't seem to work well with this add-on , unfortunately. If you bring in the add-on without running the power command, many of the other commands don't work. If you have manually pulled down the repo of a project whose machine name matches the machine name of the DDEV environment (without cloning the repo to the environment root) then running the poser command will replace many of the intended files with aliases that point to invalid references, and it will nuke the got repo. Not ideal.
Describe your solution
I wish there was a version of this add-on that only provided the static analysis and testing tools that mirror what's in Gitlab CI. If that existed, the his add-on could pull that in to maintain the current functionality, but sites that wanted to take a different approach could still benefit from the static analysis and other tests.
Describe alternatives
No response
Additional context
No response
Is there an existing issue for this?
Is your feature request related to a problem?
I love the idea of this add-on, bit it makes one fundamental assumption that makes it difficult for me to work with: it assumes that each environment is meant to work with one (and only one) contribution project. On practice, as the maintainer of dozens of contrib projects, I often prefer the opposite. I want to have a single site with lots of different modules pulled in as got repos, and it is immensely useful to have DDEV snapshots that have one or more projects installed with relevant data and settings.
That kind of workflow doesn't seem to work well with this add-on , unfortunately. If you bring in the add-on without running the power command, many of the other commands don't work. If you have manually pulled down the repo of a project whose machine name matches the machine name of the DDEV environment (without cloning the repo to the environment root) then running the poser command will replace many of the intended files with aliases that point to invalid references, and it will nuke the got repo. Not ideal.
Describe your solution
I wish there was a version of this add-on that only provided the static analysis and testing tools that mirror what's in Gitlab CI. If that existed, the his add-on could pull that in to maintain the current functionality, but sites that wanted to take a different approach could still benefit from the static analysis and other tests.
Describe alternatives
No response
Additional context
No response