Cas Donoghue comments

Results 123 comments of


                                            Cas Donoghue

Error running multiple tasks on a single target node at one time

Thanks this should be fixed in the latest PE version

(maint) trace docker transport run_cmd

Are you saying that the trace logging with upload_file https://github.com/puppetlabs/bolt/blob/ca25a6bed9b1ea70e8b03d88597c7ad935140dfe/lib/bolt/transport/docker/connection.rb#L100 is not working? I dont think we log run_command in the other transports in the connection class, was this a...

Docs not deployed?

We will get the docs deployed at the next bolt release. thanks

Apply does not work on local transport with bundled-ruby=false for latest puppet 7 agents

This actually was an issue with the local transport itself (see linked PR). I went ahead and bumped gem deps anyway https://github.com/puppetlabs/puppet-runtime/pull/735

Apply does not work on local transport with bundled-ruby=false for latest puppet 7 agents

yep

dependabot: check for github actions and bundler

Given we handle packaging of gems the system packages we build, i dont want automation to be bumping dependencies at the component level.

dependabot: check for github actions and bundler

For this particular repository we are trying to manage two streams (PE LTS and STS) with a single bolt version. The LTS is ruby 2.7 based and the STS is...

dependabot: check for github actions and bundler

I think i'm confused about what these actions actually do... puppet-runtime is the definitive source about what gems actually get shipped in bolt packages. These obviously must satisfy the requirements...

r10k: Require 4.x & octokit: Allow newer versions & puppetlabs_spec_helper: Require 7.x

I think we can drop 2.5 for bolt 4.

r10k: Require 4.x & octokit: Allow newer versions & puppetlabs_spec_helper: Require 7.x

The only reason we've kept 2.5 is for some internal testing on older OS. I was thinking of updating all that when we move to making the default ruby 3...