Jira (BOLT-864) Always upload code from bolt when running a task via Orchestrator

3 views
Skip to first unread message

Michael Smith (JIRA)

unread,
Oct 10, 2018, 6:11:05 PM10/10/18
to puppe...@googlegroups.com
Michael Smith updated an issue
 
Puppet Task Runner / New Feature BOLT-864
Always upload code from bolt when running a task via Orchestrator
Change By: Michael Smith
Summary: Always upload code from bolt when running a task via Orchestrator
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Alex Dreyer (JIRA)

unread,
Nov 13, 2018, 12:20:03 PM11/13/18
to puppe...@googlegroups.com

Paul Schaffer (JIRA)

unread,
Dec 7, 2018, 4:33:03 PM12/7/18
to puppe...@googlegroups.com

Adam Bottchen (JIRA)

unread,
Jan 24, 2019, 6:35:03 PM1/24/19
to puppe...@googlegroups.com

Sean Millichamp (JIRA)

unread,
Jan 24, 2019, 7:03:09 PM1/24/19
to puppe...@googlegroups.com
Sean Millichamp commented on New Feature BOLT-864
 
Re: Always upload code from bolt when running a task via Orchestrator

Please don't make this an "always" behavior. It should be an option, definitely.

I have use cases where users can run tasks on certain targets, but only if those tasks have been peer-approved, tagged, and released to production. Just because they have restrictions from a compliance standpoint doesn't mean they don't want to be able to use the Bolt CLI.

 

Reid Vandewiele (JIRA)

unread,
Jan 24, 2019, 7:26:06 PM1/24/19
to puppe...@googlegroups.com

For context, this is the basic use case driving this feature request.

As a [Puppet Task developer],
When [iterating on and developing changes to a Puppet Task],
When [the transport I have available is pcp],
I want [the Task code from my workstation to be used when I invoke `bolt task run`],
so that [I can iterate and develop without needing to `git commit` and deploy every edit].

There are other use cases served by the current, existing behavior. We certainly don't want to lose those use cases, but it's probable that the current behavior will migrate to, and become the opt-in behavior eventually, with behavior that supports the above use case becoming the default out-of-box experience.

Definitely don't want to lose entirely the option of using the current-esque behavior for RBAC and central definition of task purposes.

Alex Dreyer (JIRA)

unread,
Jan 25, 2019, 11:27:04 AM1/25/19
to puppe...@googlegroups.com
Alex Dreyer commented on New Feature BOLT-864

Sean Millichamp Is there a reason to prefer bolt for that over the puppet task cli? Are they run as part of plans? Do they run over ssh and pcp in the same commands?

Reid Vandewiele (JIRA)

unread,
Aug 29, 2019, 6:35:02 PM8/29/19
to puppe...@googlegroups.com

Austin Boyd (JIRA)

unread,
Dec 5, 2019, 6:16:04 AM12/5/19
to puppe...@googlegroups.com
Austin Boyd updated an issue
 
Change By: Austin Boyd
Zendesk Ticket IDs: 32992
Zendesk Ticket Count: 1
Reply all
Reply to author
Forward
0 new messages