vendor/lakedrops/docker4drupal/ahoy.current.yml defines the commands for interacting with the live database. If config split is not installed on your project, these commands fail with the following output:
There are no commands defined in the "config-split" namespace.
Is it pedantic of me to request config_split module to be listed as a requirement of Lakedrops enabled Drupal projects?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Thanks @rominronin for reporting this, I fall into this trap before as well. In my case, it was a demo project and I didn't bother too much about it, since all our other projects always use config-split.
I would probably not declare config-split as a dependency because that wouldn't be sufficient. The script also requires that to be enabled and configured, which is not happening automatically.
Instead, I think we could probably make the script smarter and let it skip those commands if config-split isn't available.
Hi @rominronin I was already on this and added a check whether config-split is enabled. The import only gets executed if that's the case. Please have a look at the linked commit.
A regular config:import that you mentioned should NOT be executed here because there are regular scenarios where a developer downloads the DB from either live or current and then wants to export the config from that DB as they want to extract the changes that have been made upstream. If a config import were executed here, those changes would be lost. If a developer does want to import config from the repository/file-system, then they can call that command manually.