It is difficult (impossible?) to figure that out without looking at the source code. Add this configuration option to documentation and possibly add it to common debugging in bolt depending on if tasks will typically take longer than ~16 mins
It is difficult (impossible?) to figure that out without looking at the source code. Add this configuration option to documentation and possibly add it to common debugging in bolt depending on if tasks will typically take longer than ~16 mins
Update: * Add orch-client config options the pcp transport config for Bolt - these should just get passed through
Creating this ticket as a result of trying to debug why long running tasks are timing out. Root cause was the default {{job-poll-timeout}} in https://github.com/puppetlabs/orchestrator_client-ruby/blob/master/lib/orchestrator_client/config.rb#L40 . The issue was solved by configuring that option in {{/etc/puppetlabs/client-tools/orchestrator.conf}} on the bolt controller with something like {code} { "options": { "job-poll-timeout": 2000 } } {code} It is difficult (impossible?) to figure that out without looking at the source code. Add this configuration option to documentation and possibly add it to common debugging in bolt depending on if tasks will typically take longer than ~16 mins
Update: * Add orch-client config options the pcp transport config for Bolt