Open lgmorand opened 6 months ago
Hey @lgmorand, for unattended installation you might prefer to use helm or CI/CD tooling such as Flux or ArgoCD.
Check the docs for more info https://docs.groundcover.com/docs/getting-started/installation-and-updating
Why do you want to force people to use gitops ? :) I could but it forces me to add Flux/Argo just because I need to use groundC ?
you are providing a cli tool with parameters, especially a YES_FLAG but it's not fully implemented. it you want to force it to be interactive, you should create a GUI instead. each cli in the world can be unattended but not yours. That's fine to me, but don't expect me to use it at Microsoft nor to push it to our customers if I feel, it won't match our Cx integration process (and it's sad because your tool itself is cool ;))
Hey @lgmorand , you can run the cli tool using the --yes
flag, for example: groundcover deploy --token ${token} --yes
. Which will not prompt you for approvals, AKA without any human interaction.
Let me know if it did the trick for you.
Thanks Max. I'm running my workflow to deploy groundclover. Will come back here to confirm if now, the yes flag is taken into account.
sh -c "$(curl -fsSL https://groundcover.com/install.sh)"
chmod +x groundcover
groundcover deploy --yes --token XXX
for the moment, it fails with a exec permission denied. will continue to dig in
Is it possible to install it without any human interaction ?
At some point, it asks for confirmation but it prevent any non interactive installation. did I miss a cli parameter ?
I found "ASSUME_YES_FLAG" in the source code but found no way to set it up