I like the Wizard. It simplifies the hazzle around the certificates considerably.
But couldn't it be extended to a configuration file that contains all necessary information instead of playing a question and answer game?
This would make it a bit easier to apply for a certificate.
icinga2 node wizard --file q_and_a.ini
icinga2 node wizard
(followed by some questions)
In my current environment (container and automation) I use expect to get the desired result.
That's not really important.
But it would be a nice addition.
What about the node setup cli command? Does that not fill your automation needs?
just icinga2 node wizard to create an (satellite) certificate.
currently i use expect for the needed answers: https://github.com/bodsch/docker-icinga2/blob/master/rootfs/init/node-wizard.expect
That's very much not the intended use for the node wizard command :P
I think it would be much better to improve the node setup command to cover this use case. Can you collect which options the node setup command is missing to be used in your case?
Well, the node wizard creates a certificate request for a satellite.
I think that's what it's for.
But I have no idea to what extent you can change the node setup to meet my requirements.
We could meet in November for the OSMC ...
I don't like the idea to add yet another method to run the setup wizards. Although a seed file similar to Debian packages sounds legit ... Still, I would advise to use node setup instead for automated setups.
As far as I understand it is not possible to configure a client using node setup without mentioning a ticket number. Without using puppet or similar configuration management tool it is a hassle to deploy a larger environment on Linux. Would be great to either enhance node setup to be used with ticketless On-Demand CSR Signing or node wizard with some kind of non-interactive mode.
Unfortunately we have no plans to implement this.