https://www.puppet.com/community logo
Join Slack
Powered by
This message was deleted.
# bolt
s
This message was deleted.
s
I'm sure there is something environmental about an Orchestrator-executed Bolt plan which I could examine, but I haven't dug into that execution environment much yet to just know what it is.
v
transport in the config
s
hmm... I'll check again, but in my testing the targets from an Orchestrator plan seem to not set transport - taking the default of ssh. maybe fixed in a newer PE version. I'm on LTS
and, unfortunately, even if the Orchestrator set all the targets to protocol==pcp, you can also have protocol=pcp from a Bolt via Orchestrator run
b
there is no reliable way
I requested that 2.5 years ago
😞 1
s
I' m going with:
Copy code
system::env('HOME') == '/opt/puppetlabs/server/data/orchestration-services'
for now
I don't love it, but it works for my purposes
b
that function istn available in PE plans
s
not knowing any better, I just ran it and it worked!
b
I had the same idea in the past :D
mhm
which PE version
s
2021.7
b
s
someone didn't tell the docs team. or the functions folks. lol
b
@steveax can you help us out? :)
s
it are some of those very limitations I'm trying to detect and account for
it is super frustrating
b
do you call it in a block?
s
no
b
mhm
interesting
s
Yeah, the only thing off the top of my head is trying one of the unsupported things and catching, feature testing essentially. @Cas Donoghue , thoughts?
s
also very frustrating is the inability to use set_feature. I'd like to use the implementations task feature to switch between a Python 2 task and Python 3 task (need different shebangs for the "python2" vs. "python3" interpreters, at a minimum.
overall, the more I use it the more I am disappointed by what feels like a half-way finished plan implementation in PE 😞
b
yeah :(
I hear that from a few customers
s
it is like... so close to being amazing. but all the edges just make it almost more trouble than it is worth
Open in Slack
PreviousNext
Powered by