#theforeman

afisher: sorry i had to dash, did you figure out an enc solution for octocat?

gwmngilfen: Not really

its a tricky one yeah, i never came up with a good solution for the plugin to use either (my demo just uses the same enc twice)

How were you running it? Were you getting it to run puppet itself, or use the API like me?

mmmm

*february

I might just build a second puppet server. I can configure it with the same role, but with one small difference. Add --no-environment to the call to the ENC.

iirc i was supplying the path to the binary, the facts cache (in /opt) and the path to the enc script

so the puppet server wasn't involved

but i still needed a solution for where you have vastly different modules/params in the new env, since foreman won't have that data

the best I could think of was to allow a text editor where you could custom craft the second env's enc

I think I don't have those issues as I'm not assigning class parameters in Foreman (just a role class which includes profiles that lookup data from hiera)

so, env aside, your enc looks the same between envs anyway?

hey, is it possible to set "PUT /api/hosts/:id/boot" via hammer?

That would be the plan. Still use the foreman ENC as I want to know what role is assigned and need a few parameters (tier, role, project etc) for the hiera hierarchy.

afisher: so what binds you to running it through the puppet server then? can you not call it directly as I was (which would allow you to mess with the enc)?