Puppet » Puppet Dashboard

Using split() indeed works “fine”. Unless you

• migrate from another tool that supports arrays (like site.pp or any other external node script)
• have quoting problems
• don’t want to have to remember which delimiter you need for each variable

I’d really prefer to have arrays input in the UI as multi- fields and have them saved in the database properly. This obviates the need for any quoting or other munging in the UI, the op’s head or the manifest, because the produced YAML would already have a real array.

Lets be serious though – more complex structures will be what is asked for next – like hashes – arrays of arrays etc. etc. Thinking in this direction will cause theoretical conundrums (and head explosion) but should be powerful enough to model anything people throw at the tool. For some reason my mind drifts towards couchdb style documents :–).

I’ve just hit this issue. It is indeed annoying. Do we have any examples of a workaround using split() ?

An example of the use of split() Hopefully this is useful for some people. in Dashboard i define fw_type as a comma separated string.

class amodule::server {

if ( ! $fw_type ) or ( $fw_type == '' ) {
err( "amodule::server requires a fw_type!" )
exec { "echo 'amodule::server requires a fw_type!'; exit 1": }
} else {
$fw_type_array = split( $fw_type, ',' )
amodule::server::type{ $fw_type_array: }
}

}

define amodule::server::type() {

$fw_type = $name
.....

}

The ENC probably also needs maps added at the same time. The UI and communication paths should be approximately the same for handling both, I expect, at least at the YAML level.

Triage-A-Thon: Duping #6583 to this one as this was here first.