Yes Below is the error message Unable to fetch archive,the source parameter is nill Code: archive { "${s3path}/test/${app_file_name}" : ensure => 'present', path => "${s3path}/test/${app_file_name}", user => $test_user, group => $test_group, extract => true, extract_path => $runtime_dir, creates => "${runtime_dir}/test/conf" }

well, as the error says, you're not setting a source parameter

It looks like that resource definition is expecting

source

to default to

title

.

Better to set a descriptive title for human reading and debugging and put the resource data into

source

. Same with using

message

instead of

title

for

notify

and

command

instead of

title

for

exec

.

Thanks got it .looks like silly issue .S3 bucket file and yaml defined file has a minor typo

Thanks all

Finally fixed the pup7/centos7 acceptance test over at https://github.com/voxpupuli/puppet-hocon/pull/1; it's all running green now

I fixed that stubborn pup7/centos7 acceptance test over at https://github.com/voxpupuli/puppet-hocon/pull/1; it's all running green now

After puppet-hocon is merged, then https://github.com/voxpupuli/puppet-puppet_authorization/pull/1 is ready

After puppet-hocon is merged, then https://github.com/voxpupuli/puppet-puppet_authorization/pull/1 is ready

Finally fixed the pup7/centos7 acceptance test over at https://github.com/voxpupuli/puppet-hocon/pull/1; it's all running green now

can someone point me at documentation for voxpopuli and modutil merges please?

@Grant Diffey what kind of docs do you have in mind? https://voxpupuli.org/docs/reviewing_pr/

Yeah: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/puppet_x/stdlib/toml_dumper.rb

Yeah: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/puppet_x/stdlib/toml_dumper.rb

@bastelfreak I was thinking specifically of how the modutils merges are created (that update tooling and test cases aiui?

I am not sure if I understand the question. we work with pull requests and in the end PRs are merged which results in a merge commit.

with modutils you mean puppet modules?

I thought there was a common 'framework' somewhere that was causing the pdk/module test framework updates across all the modules?

ahh okay. so pdk can apply boilerplate code. the official template repo for pdk is https://github.com/puppetlabs/pdk-templates

ahh okay. so pdk can apply boilerplate code. the official template repo for pdk is https://github.com/puppetlabs/pdk-templates

at vox pupuli, we dont use pdk for various reasons. we use https://github.com/voxpupuli/modulesync to manage the boilerplate staff. our templates are at https://github.com/voxpupuli/modulesync_config

at vox pupuli, we dont use pdk for various reasons. we use https://github.com/voxpupuli/modulesync to manage the boilerplate staff. our templates are at https://github.com/voxpupuli/modulesync_config

that's what I was asking about 🙂

can I get a review for https://github.com/voxpupuli/puppet-augeasproviders_ssh/pull/76

and https://github.com/voxpupuli/puppet-augeasproviders_ssh/pull/77

Okay if I move https://github.com/traylenator/puppet-zram_generator to VoxPup space. Will finish of the templating once there.

frisbee: I would be fine with that if you take care of modulesyncing