Hey all. I am adding a yaml file to a host and configuring it an an epp like:

signers:
  user:
    key: |
      <%= $user_ca %>

The contents of user_ca is a private key; however, when I do this, the outcome is:

signers:
  user:
    key: |
      -----BEGIN OPENSSH PRIVATE KEY-----
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXX
-----END OPENSSH PRIVATE KEY-----

The first line is correct, but the ones at the bottom are not inline with the top. Is there a way to ensure they are all aligned with the top line?

@ziggy I would rather try

{ signers => { user => { key => $user_ca } } }.to_yaml

, that is generate a data structure that match what you want and serialize it to YAML

@ziggy I would rather try

{ signers => { user => { key => $user_ca } } }.to_yaml

, that is generate a data structure that match what you want and serialize it to YAML

oh! Thank you

you can also try fiddyspence/hash_file

See the

fiddyspence-hash_file

module at https://forge.puppet.com/fiddyspence/hash_file?src=slack&channel=puppet

ok with no shouts of pain these have been archived and set to read only into the toybox. A blog post will be released to clarify this and the future direction of PDK https://github.com/puppetlabs-toy-chest/pct https://github.com/puppetlabs-toy-chest/prm

ok with no shouts of pain these have been archived and set to read only into the toybox. A blog post will be released to clarify this and the future direction of PDK https://github.com/puppetlabs-toy-chest/pct https://github.com/puppetlabs-toy-chest/prm

This message was deleted.

This message was deleted.

```- took a hit! Ouch. (Karma: -107)

There is a quite old ticket about it https://tickets.puppetlabs.com/browse/SERVER-2355

This message was deleted.

file_line is a paqrt of the stdlib module: https://forge.puppetlabs.com/modules/puppetlabs/stdlib/reference#file_line

the stdlib may as well be considered "core" since it is "standard"

Generally speaking, you can trust anything produced by Puppet on your system. Core functionality for pretty much all supported or affiliate modules is usually offered by puppetlabs/stdlib

See the

puppetlabs-stdlib

module at https://forge.puppet.com/puppetlabs/stdlib?src=slack&channel=puppet

This message was deleted.

I'm writing out a puppet module and got into a debate with a coworker about what would be the best way to write it and wanted to see what opinions were: Let's say I'm creating a puppet module that does three things: 1) installs an application, 2) creates a config file from a template, and then 3) ensures the application service is running (on linux). I've gone the route such that my module hierarchy is:

| hieradata
|   -> defaults.yaml
|
| manifests
|   -> init.pp
|   -> install.pp
|   -> config.pp
|   -> service.pp
|
| templates
|   -> config.yaml.epp

The idea is that the init.pp just does a contain on the other 3 subclasses (install, config, and service). The install subclass will contain the functions for installing the application as well as any parameters related to the install:

class module::install(
  String $package_version
) {}

The config subclass will generate and place the config file on the server as well as contain any parameters related to the config. The service subclass will ensure the service is in a given state and will contain any parameters related to the service. My coworker proposed that instead all of the parameters actually be defined within the init.pp class. I felt it was better to put parameters in the subclasses they belong to as a means of being more organized but what are your thoughts?

This message was deleted.

message has been deleted

user interact with a module via init class's parameters

message has been deleted

This message was deleted.

though it’s well aligned with the idea of having the init.pp as the only entry point (interface) of the module

Appreciate it everyone!

This message was deleted.

This message was deleted.