| I've chatted with a few customers in the past who want use to bolt + PE in a self service manner i.e. devs using bolt (no PE access) to run tasks through PE/orchestrator. It really seems to land well with folks who aren't embracing dev op's today and want to move in that direction - they really see the value. Running PE tasks via Bolt is possible today through the PCP transport however, the ability to view said tasks from PE using bolt is not. My understanding is that if you want to view those tasks or perform a run, you'll need to install PE client tools and then run puppet task show rather bolt task show...then you would switch back to bolt to run the task, now that you know it exists which is a little counter intuitive and it definitely feels little odd when explaining that to a customer (recently had this convo with the DevOps lead at Freshfields Bruckhaus Deringer). Other things like kicking off puppet runs via bolt/orchestrator would make sense too. So I think in this scenario I'm suggesting, Bolt could almost replace client tools in regards to PE orchestration functionality. So, you can have bolt be a totally independent tool when not using PE but when used with PE, it becomes the defacto under the hood operator. I feel like it makes sense from a usability perspective and it would definitely help increase the daily usage of the tool in total but this is probably way more complex than I understand and would take a ton of work to make something like this happen, but I thought it'd be worth sharing. I raised this in the bolt room and I've included some of the conversation below for ref. adreyer [Yesterday at 16:52]
To be a bit clearer @marc once Orchestrator has the ability to run plans we don’t think there will be much of a use case for the existing running plans or tasks over pcp transport. There is some question about whether it’s better to have bolt behave in two complete different modes based on whether it’s doing things locally vs on orchestrator or whether it’s better to have a separate cli command for the orchestrator client instead of bolt. marc [1 day ago]
@adreyer thanks for clearing that up - +1 for bolt w/different modes rather than the latter. It seems to make more sense from usability/consistency perspective - start with bolt, use existing scripts > turn them into tasks/plans > migrate them to PE and then continue to use that same tool to drive PE, under the hood. So you’re continuing to use bolt but it’s not doing the heavy lifting anymore. (edited) |
