Create 'l3d info' or 'l3d status' to provide helpful debugging output
It would be cool to have an 'l3d info' or 'l3d status' command to output the current used values and settings, and maybe to do some basic check if everything is setup properly.
It would be cool to have an 'l3d info' or 'l3d status' command to output the current used values and settings, and maybe to do some basic check if everything is setup properly.
added To Do label
assigned to @jurgenhaas
removed To Do label
added Doing label
I think this is a great idea. I'd go for l3d info
and it came to my mind that a user could actually call l3d on the host or (maybe accidentally) inside a l3d container. The latter would currently lead to an error because l3d doesn't exist inside a container. We can change/fix that by the same time and go for this:
If l3d info
is called on the host, we run some analysis and output as much useful information we can possibly find. When this framework exists, it will be easy to add to this later on when we recognize more useful components.
For l3d info
inside a container, we only output useful information for the current container. And while building that, if a user calls l3d inside the container with other arguments, then we can output a message, that this is only possible outside of the container.
mentioned in commit 7984e37b
mentioned in commit 17f42b3e
mentioned in commit d4d57bd9
mentioned in commit 86fc4c0b
mentioned in commit f9c90661
mentioned in commit gitlab-drupal-ci@28f2f5e4
mentioned in commit 63098a2f
mentioned in commit 0c18ab4b
closed
removed Doing label