Rundeck Rundeck Development

I would like for rundeck to integrate closer with Puppet and there are a number of things that could be done to improve this. One of the first things that would ease our use cases significantly would be to add 'Puppet Manifest' to the list of steps when building a job.

This would then give you a box like script and allow you to put in a manifest:

file { "/var/www/html/sms-server/smsconfig.inc":

ensure => present,
source => "puppet://puppet/modules/x/var/www/html/sms-server/@option.role@/smsconfig.inc",

}

file { "/var/www/html/sms-server/smsconfig_vendors.inc":

ensure => present,
source => "puppet://puppet/modules/x/var/www/html/sms-server/@option.role@/smsconfig_vendors.inc",

}

As you can see there's an option.role in there that would be, obviously, populated before the next step. Then something like:

sudo -s puppet apply --modulepath=@modulepath@ /tmp/generated.pp

Would be ran, with modulepath coming from somewhere definited in rundeck (or overwritten at the job level). You might want to be able to define the base elsewhere and then the environment in the job so it would be more like --modulepath=@x@/@y@/ where @x@ is /etc/puppet/modules/ and @y@ at the job level is development.