Hello,
I would like to use gcp key management for eyaml encryption/decryption, and
was excited to see that https://github.com/craigwatson/hiera-eyaml-gkms
looked to be just what I needed! Initial testing worked great, but I ran
into a wall when trying to get puppetserver to use it.
Trying t
Hello,
As I've been building up my puppet infrastructure, I've started using
puppet certs for all of my services that require ssl. Usually this is
in the form of links:
file {
"/opt/syslog-ng/etc/ca.d/b2457b50.0":
require => Package["syslog-ng"],
ensure => li
Thanks Pete! I owe you a beer. Using defines this way works much better.
And, for my issue with adding options, it's just a matter of passing in the
options to the define, then using:
ssh_keys::bob{"repo": options => "command=\"svnserve -t
--tunnel-user=bob\""}
Often it's hard for me to get in
Correction: "seems to work as expected" :) overriding name gets it to the
"repo" user, but does not keep in other places. Looks like I'm back to using
variables. Thanks for the tip.
--Bob
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To pos
Alan,
You just reminded me that the name has to be unique. It turns out it will
work when inherited, but you have to override the name as well. This works
as expected:
class repobob inherits ssh_keys::all::bob {
Ssh_authorized_key[bob] {
user=> "repo",
na
Hello,
I'm trying to reuse an ssh_authorized_key, but I'm having some problems.
There was a recent thread about using the same key for different users, but
I didn't see any resolution there. My issue is a bit different. I'm
currently using this key:
class ssh_keys::all {
class bob {
