Jira (BOLT-335) Boltlib functions should have configurable timeouts

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen created an issue   Puppet Task Runner / BOLT-335 Boltlib functions should have configurable timeouts Issue Type: Improvement Affects Versions: BOLT 0.16.1 Assignee: Unassigned Created: 2018/02/13 5:53 PM Priority: Normal Reporter: Charlie Sharpsteen Consider the following task plan: plan do_a_thing ( Array[String[1]] $nodes, ){   # About to do something that a puppet run would conflict with. run_task('disable_puppet', $nodes)   # I know this should fail in 30 seconds. Or that it's a long database migration and might # take up to 3 hours. run_task('some_transaction', $nodes)   run_task('enable_puppet', $nodes) } Functions from boltlib like run_task, run_plan, run_command, run_script, file_upload, etc. should have a timeout parameter that can be used to set an expectation for when a command should finish so that guarantees can be made around when a temporary state, like pausing puppet, will be reset at the conclusion of the plan. The timeout should be configurable per-task so that operations which should finish fast can be failed fast and operations which are expected to take a long time are not interrupted early. Add Comment   This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.