Ensure Cachet Commands Respect `--no-interaction`
In particular, the cachet:install command needs to select good defaults automatically (if it can). Perhaps we should allow the command to create an sqlite database on disk?
We did start this, but I think providing sensible defaults is the best option, including generating a password for an admin account.
but I think providing sensible defaults is the best option
Yeh, then with sensible defaults, --no-interaction will work properly.
This bug extends to the framework core commands too.
@GrahamCampbell where are we about this feature ? Do you know if we can user cachet:install without any interaction in a salt recipe for example (with an admin account created) ?
The idea would actually be that the command crashes and says you have to run it with interaction. Rather than just hanging forever waiting for input.
@GrahamCampbell thx for answer, so you mean that for now we can't fully install and configure cachet from a script or a salt recipe ?
Hey, is there an update regarding this? I looked for a way to automate the initial setup of cachet but couldn't find a way. Thanks.