sounds like your setup is different? you've multiple modules in a monorepo and want to deploy them via Puppetfile?

I saw a monorepo where all modules were vendored.. so just no Puppetfile was required

I was even able to make modules management via Bolt there.. but nobody was able to understand how great it was… :-D

yeah. just add the correct path to environment.conf and it works out of the box

I checked through https://www.puppet.com/docs/pe/2023.1/puppetfile.html#specify_installation_paths_for_repositories and I knew the option to install a module into a different directory. But I thought there's also an option to only install a subdir from a module, bu I cannot find that option

ah yes that version on monorepo i have done before, i am talking about https://monorepo.tools/ where all the code for all the projects (also product and infra) are in the same single git repo. Supposed benefits are that cross project changes can all land in the same MR/PR but of course kills of any chance of using a "standard" workflow. So am really trying to work out something like.

mod 'profiles',
    :git => 'git@github.com:$org/monorepo.git/$infra-team/puppet/modules/$org-profiles

I checked through https://github.com/puppetlabs/r10k/blob/main/doc/dynamic-environments/configuration.mkd and didn't find an option to deploy a control-repo from a subdir of a module

so either I'm too stupid to find that option or you would have to implement this

i was afraid you were going to say that

I'm happy to review your patches 😄

Is there a native way to call by current module name in hiera.yaml datadir? path: "%{module_name}.yaml"

it's relative to the datadir setting, why do you need absolute path, curious ?

I want to store all the data under the datadir. I have a case where I want to store data under the module name it's tied to. That way at a glance if I need to change the data for that mod it's right there.

I can't seem to find a way to call by module name. I know I can place the data with the module but I was hoping to keep it all under one location

you can specify some absolute path in datadir and keep it in that location, but module_name is not available, at least I don't think so

I don't think hiera is even aware of 'module'

i did something similar, but that is a bit hacky. i added a facter script that read all module names from the last run report (would have to look up how i did it again). and then i used "mapped_paths: [modules_fact,module,"modules/%{module}.yaml"]" do "dynamically" load data based on the applied modules of the last run

the problem was that its a bit of a hen and egg problem i think, do you load the hiera facts first or apply the modules first. i think puppet usually first gets the facts and then applies the modules when it has all the "base" data

aditionally: i think my workaround is broken right now, so dont put too much faith in that 😛

Yeah, sounds like I should just use a module yaml for this one

this seems like the entire point of the module's yaml and profiles

yea, but module yamls dont really work for official modules and profiles have their own problems ^^

that all sounds... odd 😄

@Tom Hilburn why not store the data in the module itself?

@bastelfreak I wanted to keep all of the data under one spot. The datadir

mhm

I'm not convinced!

goodnews 🧑‍🏫 Bolt is about to start up in #CFD8Z9A4T

This message was deleted.

See the

binford2k-node_encrypt

module at https://forge.puppet.com/binford2k/node_encrypt?src=slack&channel=puppet