[dev.icinga.com #12652] CA handling using custom function from puppet-icinga2-legacy

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12652

Created by bsheqa on 2016-09-06 07:48:24 +00:00

Assignee: (none)
Status: Closed (closed on 2016-12-14 08:16:26 +00:00)
Target Version: v0.7.0
Last Update: 2016-12-14 08:16:26 +00:00 (in Redmine)

---

---

Relations:

• relates #12652

[icinga-migration]

Updated by bsheqa on 2016-09-20 18:07:34 +00:00

• Target Version changed from v0.6.0 to v0.7.0

[icinga-migration]

Updated by bsheqa on 2016-09-26 14:19:18 +00:00

• Relates set to 12801

[icinga-migration]

Updated by bsheqa on 2016-12-13 12:28:22 +00:00

• Status changed from New to Feedback

I need feedback on this branch: https://github.com/Icinga/puppet-icinga2-rewrite/tree/feature/certificate-signing-12652

[icinga-migration]

Updated by lbetz on 2016-12-13 18:58:57 +00:00

Looks good. And it works? icinga2 pki save-cert --host '${ca_host}'${_ca_port} --key ... looks strange.

Maybe it's a good idea to use a default ca_port? 5665.

[icinga-migration]

Updated by bsheqa on 2016-12-14 07:59:51 +00:00

Yes it works. The command sets port 5665 by default if no port is provided. But in Puppet its probably better readable to set 5665 explicitly as default.

[icinga-migration]

Updated by bsheqa on 2016-12-14 08:16:26 +00:00

• Status changed from Feedback to Closed
• Done % changed from 0 to 100