Jira (BOLT-677) Bolt does not serialize complex types as JSON with environment input method
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-677 Bolt does not serialize complex types as JSON with environment input method Change By: Michael Smith Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog Change By: Michael Smith Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-634) Integration tests for apply functionality
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-634 Integration tests for apply functionality Change By: Michael Smith Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-647) Support _noop for apply statements
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-647 Support _noop for apply statements Change By: Michael Smith Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8783) Extract the code & verify the module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8783 Extract the code & verify the module Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-630 PowerShell based tasks throw an error about a non-existant parameter Change By: Cas Donoghue Release Notes Summary: PowerShell standard argument handling will only be used for parameters explicitly declared in PowerShell tasks when input_method is set to powershell. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8579) Extract yumrepo type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8579 Extract yumrepo type/provider into a module Change By: Josh Cooper Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8579) Extract yumrepo type/provider into a module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8579 Extract yumrepo type/provider into a module Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8850) Remove type/provider code from puppet
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8850 Remove type/provider code from puppet Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8851) Move all outstanding PUP tickets to Modules
Title: Message Title Josh Cooper commented on PUP-8851 Re: Move all outstanding PUP tickets to Modules I could only find one ticket PUP-661 to remove the broken macauthorization provider. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Cas Donoghue commented on BOLT-630 Re: PowerShell based tasks throw an error about a non-existant parameter https://github.com/puppetlabs/bolt/pull/497 fixes the original error by only passing expected parameters. Original error: System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name '_task'. Upon attempting to run the wsus_client::update_history task a new failure occurred. This failure: HRESULT is WU_E_INVALIDINDEX is a windows update error code. BOLT-628 was created proposing better error handling for powershell tasks. C:\cygwin64\home\Administrator\bolt>bundle exec bolt task run wsus_client::update_history --transport winrm --nodes localhost --user Administrator --password --no-ssl bundle exec bolt task run wsus_client::update_history --transport winrm --nodes localhost --user Administrator --password --no-ssl Started on localhost... Failed on localhost: The task failed with exit code 1: $private:tempArgs = Get-ContentAsJson ( : System.Runtime.InteropServices.COMException (0x80240007): Exception from HRESULT: 0x80240007 at System.Management.Automation.ComInterop.ComRuntimeHelpers.CheckThrowException(Int32 hresult, ExcepInfo& excepInfo,
Jira (BOLT-678) Improve powershell task error handling
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-678
Improve powershell task error handling
Change By:
Cas Donoghue
While testing BOLT-630 using the https://github.com/puppetlabs/puppetlabs-wsus_client task wsus_client::update_history a WU_E_INVALIDINDEX error code was surfaced. The output (shown below) could be improved to help user debug the problem. {code}C:\cygwin64\home\Administrator\bolt>bundle exec bolt task run wsus_client::update_history --transport winrm --nodes localhost --user Administrator --password --no-sslbundle exec bolt task run wsus_client::update_history --transport winrm --nodes localhost --user Administrator --password Qu@lity! --no-sslStarted on localhost...Failed on localhost: The task failed with exit code 1: $private:tempArgs = Get-ContentAsJson ( : System.Runtime.InteropServices.COMException (0x80240007): Exception from HRESULT: 0x80240007 at System.Management.Automation.ComInterop.ComRuntimeHelpers.CheckThrowException(Int32 hresult, ExcepInfo& excepInfo, ComMethodDesc method, Object[] args, UInt32 argErr) at CallSite.Target(Closure , CallSite , ComObject , Int32 , Object ) at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2) at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2) at System.Management.Automation.Interpreter.DynamicInstruction`4.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException { }Failed on 1 node: localhostRan on 1 node in 1.91 seconds{code}
Add Comment
Jira (BOLT-678) Improve powershell task error handling
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-678 Improve powershell task error handling Issue Type: Improvement Affects Versions: BOLT 0.21.1 Assignee: Unassigned Created: 2018/07/03 2:44 PM Priority: Normal Reporter: Cas Donoghue While testing BOLT-630 using the https://github.com/puppetlabs/puppetlabs-wsus_client task wsus_client::update_history a WU_E_INVALIDINDEX error code was surfaced. The output (shown below) could be improved to help user debug the problem. C:\cygwin64\home\Administrator\bolt>bundle exec bolt task run wsus_client::update_history --transport winrm --nodes localhost --user Administrator --password --no-ssl bundle exec bolt task run wsus_client::update_history --transport winrm --nodes localhost --user Administrator --password Qu@lity! --no-ssl Started on localhost... Failed on localhost:
Jira (PUP-8699) puppet device application should support outputting facts
Title: Message Title Josh Cooper commented on PUP-8699 Re: puppet device application should support outputting facts Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/de0743ae7dce3b7e19d2efb6e77398727c981ee0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8699) puppet device application should support outputting facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8699 puppet device application should support outputting facts Change By: Josh Cooper Fix Version/s: PUP 5.5.3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8849) Package module into puppet-agent
Title: Message Title Josh Cooper commented on PUP-8849 Re: Package module into puppet-agent We won't be packaging this module into puppet-agent. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-634) Integration tests for apply functionality
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-634 Integration tests for apply functionality Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-677) Bolt does not serialize complex types as JSON with environment input method
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-677 Bolt does not serialize complex types as JSON with environment input method Change By: Michael Smith Affects Version/s: BOLT 0.21.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-677) Bolt does not serialize complex types as JSON with environment input method
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-677 Bolt does not serialize complex types as JSON with environment input method Change By: Michael Smith Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8808) Remove type/provider code from puppet
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8808 Remove type/provider code from puppet Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-662) Handle task parameters in transport api
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-662 Handle task parameters in transport api Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-665) Bolt 0.21.2 2018-07-05 Release
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-665 Bolt 0.21.2 2018-07-05 Release Change By: Michael Smith Bolt 0.21.2 2018-07- 03 05 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-1206) Augeas lenses in modules are not loaded when using puppet apply
Title: Message Title Josh Cooper commented on PUP-1206 Re: Augeas lenses in modules are not loaded when using puppet apply It would be fairly simple to add the environment-specific module path in the augeas provider. We'd want to do this to handle puppet resource also. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-665) Bolt 0.21.2 2018-07-05 Release
Title: Message Title Michael Smith commented on BOLT-665 Re: Bolt 0.21.2 2018-07-05 Release Delayed until later in the week due to BOLT-630. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-665) Bolt 0.21.2 2018-07-05 Release
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-665 Bolt 0.21.2 2018-07-05 Release Change By: Michael Smith Summary: Bolt 0.21.2 2018-07- 03 05 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-4039) package resource doesn't find new packages in yum repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4039 package resource doesn't find new packages in yum repo Change By: Geoff Nichols Sprint: Client 2016-05-04 , Platform OS Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-1590) Replace ParsedFile with Augeas
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1590 Replace ParsedFile with Augeas Change By: Josh Cooper Labels: augeas needs_decision Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1865 Amazon Linux 2 is reported as 4 Change By: Geoff Nichols Sprint: Platform OS Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (FACT-1832) Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone.
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1832 Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone. Change By: Geoff Nichols Sprint: Platform OS Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-5559) Augeas resources do not honor standard lens path
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5559 Augeas resources do not honor standard lens path Change By: Josh Cooper Team: Coremunity Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-5559) Augeas resources do not honor standard lens path
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-5559 Augeas resources do not honor standard lens path Change By: Josh Cooper Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PDB-3957) Consider printing a warning at startup for unrecognized config elements
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3957 Consider printing a warning at startup for unrecognized config elements Issue Type: Improvement Assignee: Unassigned Created: 2018/07/03 12:51 PM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-677) Bolt does not serialize complex types as JSON with environment input method
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-677 Bolt does not serialize complex types as JSON with environment input method Issue Type: Bug Assignee: Unassigned Created: 2018/07/03 12:42 PM Priority: Normal Reporter: Michael Smith The task spec notes that complex input (not strings) should be serialized as JSON when storing in environment variables: https://github.com/puppetlabs/puppet-specifications/tree/master/tasks#environment-variables. Bolt does not do that, instead it uses to_s. For hashes in particular, this is a difficult format to deserialize. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8396) Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called
Title: Message Title Geoff Nichols commented on PUP-8396 Re: Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called This has merged up through master and is passing in CI. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (PUP-8975) Agent Functions - Spike: determine if Deferred type can be implemented w/o Rich Data
Title: Message Title Henrik Lindberg commented on PUP-8975 Re: Agent Functions - Spike: determine if Deferred type can be implemented w/o Rich Data I think the Binary vs. 8-bit-ascii is easily solvable by simply replacing instances of Binary in the catalog with ascii-8-bit string on deserialization. We would also serialize all ascii-8-bit strings as instances of Binary. Then, no matter if code is "old" or using instances of `Binary`, it would work the same way - the agent logic would receive 8-bit-ascii strings just as before. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-651) Create jenkins pipeline to build package and promote
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-651 Create jenkins pipeline to build package and promote Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-652) Add basic unit tests for bolt-transports
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-652 Add basic unit tests for bolt-transports Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-651) Create jenkins pipeline to build package and promote
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-651 Create jenkins pipeline to build package and promote Change By: Lucy Wyman *As a* developer for the consumer of the bolt-transports api*I want* to be able to install the gem*So that* I can design and test the lifecycle management of the bolt-transports utilityThe pe-bolt-service should have a pipeline to build and promote the package.To build:* This should look similar to the bolt Use pez - vanagon enabled suite pipeline , but without building the gem. to build vanagon packages * Work with RE team :) To promote:* Run package promote job Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-651) Create jenkins pipeline to build package and promote
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-651 Create jenkins pipeline to build package and promote Change By: Lucy Wyman *As a* developer for the consumer of the bolt-transports api*I want* to be able to install the gem*So that* I can design and test the lifecycle management of the bolt-transports utilityThe pe-bolt-service should have a pipeline to build and promote the package. To build:* This should look similar to the bolt-vanagon pipeline, but without building the gem. To promote:* Run package promote job Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-651) Create jenkins pipeline to build package and promote
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-651 Create jenkins pipeline to build package and promote Change By: Lucy Wyman *As a* developer for the consumer of the bolt-transports api*I want* to be able to install the gem*So that* I can design and test the lifecycle management of the bolt-transports utilityThe pe- bolt- transports gem service should have it's own jenkins a pipeline to be built build and published to internal gem mirrors promote the package . This ticket is finished when* There's a release schedule for should look similar to the gem (likely weekly releases)* A jenkins bolt-vanagon pipeline to build , but without building the gem and publish it to our internal gem mirrors* The gem can be installed from our gem mirror . Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving
Jira (BOLT-650) Separate bolt-transports to be it's own package
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-650 Separate bolt-transports to be it's own package Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-651) Create jenkins pipeline to build package and promote
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-651 Create jenkins pipeline to build package and promote Change By: Lucy Wyman Summary: Publish bolt-transports gem Create jenkins pipeline to internal gem mirrors build package and promote Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-650) Separate bolt-transports to be it's own package
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-650
Separate bolt-transports to be it's own package
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool*and so that* I can develop an end-to-end workflow with the orchestrator clientThe console team needs to have the bolt-transports API be available in PE.* the bolt transport should be a system package* it should be part of the bolt-vanagon repo* it needs an init script (what registers the service) (look to pxp-agent for prior art) * Have it use puppet-agent ruby (if possible)* This should not break or affect Bolt's build process* This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo.Questions:* What should we call the transport package? {{pe-bolt-service}}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-650) Separate bolt-transports to be it's own package
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-650
Separate bolt-transports to be it's own package
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool*and so that* I can develop an end-to-end workflow with the orchestrator clientThe console team needs to have the bolt-transports API be available in PE.* the bolt transport should be a system package* it should be part of the bolt-vanagon repo* it needs an init script (what registers the service)* Have it should have a subset of bolt's depedencies (remove deps not required by bolt-transports, mostly use puppet / pal -agent ruby (if possible )* This should not break or affect Bolt's build process* This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo.Questions:* What should we call the transport package? {{pe-bolt-service}}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-650) Separate bolt-transports to be it's own package
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-650
Separate bolt-transports to be it's own package
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool*and so that* I can develop an end-to-end workflow with the orchestrator clientThe console team needs to have the bolt-transports API be available in PE.* the bolt transport should be a system package* it should be part of the bolt-vanagon repo* it needs an init script ( {{/opt/puppetlabs/bolt-server}} what registers the service )* it should have a subset of bolt's depedencies (remove deps not required by bolt-transports, mostly puppet / pal)* This should not break or affect Bolt's build process* This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo.Questions:* What should we call the transport package? {{pe-bolt-service}}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-630 PowerShell based tasks throw an error about a non-existant parameter Change By: Kate Lopresti Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-662) Handle task parameters in transport api
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-662 Handle task parameters in transport api Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-676) Include legacy facts from ruby facter_task implementation
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-676 Include legacy facts from ruby facter_task implementation Issue Type: Task Assignee: Unassigned Created: 2018/07/03 10:01 AM Priority: Normal Reporter: Nick Lewis To support most forge modules that use facts, we need to include the legacy versions of facts in addition to the structured version (ie. $osfamily vs. $os['family']). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-649) Support _run_as as an apply option
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-649 Support _run_as as an apply option Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-648) Support _catch_errors as an apply option
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-648 Support _catch_errors as an apply option Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-647) Support _noop for apply statements
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-647 Support _noop for apply statements Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-636) Handle logging from catalog compilation
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-636 Handle logging from catalog compilation Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-636) Handle logging from catalog compilation
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-636 Handle logging from catalog compilation Change By: Lucy Wyman Logging from catalog compilation should be capture in bolts log. This may be acheived by setting up a special logger in bolt_catalog and setting it's log level, parsing log level from it, or by trying to trick puppet into doing structured logging (have puppet log and have bolt filter logs) . Does ruby logger library allow multiple processes to write to the same file? Requirements:* It should match bolts log format (i.e. no log cruft to the console)* It should match bolts log level Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-636) Handle logging from catalog compilation
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-636 Handle logging from catalog compilation Change By: Lucy Wyman Logging from catalog compilation should be capture in bolts log. This may be acheived by setting up a special logger in bolt_catalog and setting it's log level, parsing log level from it, or by trying to trick puppet into doing structured logging (have puppet log and have bolt filter logs) Requirements:* It should match bolts log format (i.e. no log cruft to the console)* It should match bolts log level Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-636) Handle logging from catalog compilation
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-636 Handle logging from catalog compilation Change By: Lucy Wyman Logging from catalog compilation should be capture in bolts log. This may be acheived by setting up a special logger in bolt_catalog and setting it's log level, parsing log level from it, or by trying to trick puppet into doing structured loggingRequirements: * It should match bolts log format( ie i.e. no log cruft to the console) * It should match bolts log level Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-635) Refactor the executor to parallelize multi-target applies
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-635 Refactor the executor to parallelize multi-target applies Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-635) Refactor the executor to parallelize multi-target applies
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-635
Refactor the executor to parallelize multi-target applies
Change By:
Lucy Wyman
When there are multiple targets for an apply the executor should compile catalogs and execute them in parallel. This will probably require some refactor of the executor. The specifics of this will require some investigationRequirements:- hard coded limit on concurrent catalog compilations separate from general concurrency- executing the catalog should not use a compilation concurrency slot Notes: - Make an async api for the executor (create callback of requirements for task)- separate {{batch_execute}} into promises section and result collection functionsFeel free to rescope break this up if needed.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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
Jira (BOLT-635) Refactor the executor to parallelize multi-target applies
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-635
Refactor the executor to parallelize multi-target applies
Change By:
Lucy Wyman
When there are multiple targets for an apply the executor should compile catalogs and execute them in parallel. This will probably require some refactor of the executor. The specifics of this will require some investigationRequirements:- hard coded limit on concurrent catalog compilations separate from general concurrency- executing the catalog should not use a compilation concurrency slot - Make an async api for the executor (create callback of requirements for task) - separate {{batch_execute}} into promises section and result collection functions Feel free to rescope break this up if needed.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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
Jira (BOLT-635) Refactor the executor to parallelize multi-target applies
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-635 Refactor the executor to parallelize multi-target applies Change By: Lucy Wyman When there are multiple targets for an apply the executor should compile catalogs and execute them in parallel. This will probably require some refactor of the executor. The specifics of this will require some investigationRequirements:- hard coded limit on concurrent catalog compilations separate from general concurrency- executing the catalog should not use a compilation concurrency slot - Make an async api for the executor (create callback of requirements for task) Feel free to rescope break this up if needed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-675) Integration testing of correct precedence
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-675 Integration testing of correct precedence Issue Type: Sub-task Assignee: Unassigned Created: 2018/07/03 9:50 AM Priority: Normal Reporter: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-674) Integration testing of correct precedence
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-674 Integration testing of correct precedence Issue Type: Bug Assignee: Unassigned Created: 2018/07/03 9:50 AM Priority: Normal Reporter: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-672) Pass vars from plan scope at higher precedence
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-672 Pass vars from plan scope at higher precedence Issue Type: Sub-task Assignee: Unassigned Created: 2018/07/03 9:49 AM Priority: Normal Reporter: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-673) Pass trusted facts
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-673 Pass trusted facts Issue Type: Sub-task Assignee: Unassigned Created: 2018/07/03 9:49 AM Priority: Normal Reporter: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Lucy Wyman The scope for manifest block compilation should be properly initialized with:From highest to lowest precedence:- facts hash (reserved, so will error if anything attempts to override it)- vars from the plan scope(excluding ephemeral variables like regex matches)- vars from the target- facts from the target$environment should be set if it is present in the plan scope or the target scope otherwise it should be unset.trusted facts should be set so that:- use host section of target for certname/hostname/domain- set authenticated: localObjects in the plan scope should be serialized and deserialized with pcore.The following values should not be set:Do not set $servername or other master variables.(maybe settings later)Do not set $server_facts(maybe version is useful? but wait for feature requests )Do not set agent facts leave that up to the fact collection step. If we need these we'll have to update the fact collection workflow. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Lucy Wyman The scope for manifest block compilation should be properly initialized with:From highest to lowest precedence:- facts hash (reserved, so will error if anything attempts to override it)- vars from the plan scope(excluding ephemeral variables like regex matches)- vars from the target- facts from the target$environment should be set if it is present in the plan scope or the target scope otherwise it should be unset.trusted facts should be set so that:- - use host section of target for certname/hostname/domain- - set authenticated: localObjects in the plan scope should be serialized and deserialized with pcore.The following values should not be set:Do not set $servername or other master variables.(maybe settings later)Do not set $server_facts(maybe version is useful? but wait for feature requests )Do not set agent facts leave that up to the fact collection step. If we need these we'll have to update the fact collection workflow. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-631) Bolt should support hiera configuration and use it when compiling catalogs
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-631 Bolt should support hiera configuration and use it when compiling catalogs Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog Change By: Lucy Wyman Bolt should pass it's module path to bolt_catalog so functions and types used in both are availableIn Scope:- All modules availabe during plan compilation should be available during catalog compilation- The TargetSpec type alias should be set up as well- Forbidden functions should error cleanly if called (everything except puppetdb_query) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog Change By: Lucy Wyman Bolt should pass it's module path to bolt_catalog so functions and types used in both are availableIn Scope: - All modules availabe during plan compilation should be available during catalog compilation - The TargetSpec type alias should be set up as well - Forbidden functions should error cleanly if called - puppetdb_query should be usable from a manifest block. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog Change By: Michael Smith Bolt should pass it's module path to bolt_catalog so functions and types used in both are availableIn Scope:- All modules availabe during plan compilation should be available during catalog compilation- The TargetSpec type alias should be set up as well- Forbidden functions should error cleanly if called - puppetdb_query should be usable from a manifest block. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-650) Separate bolt-transports to be it's own package
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-650
Separate bolt-transports to be it's own package
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool*and so that* I can develop an end-to-end workflow with the orchestrator clientThe console team needs to have the bolt-transports API be available in PE. This spike should answer: * How does the bolt -transports get installed as part of PE? transport should be a system package * The bolt transport api it should live in be part of the Bolt repository for now, preferably in bolt-vanagon repo* it 's own directory needs an init script ({{/opt/puppetlabs/bolt-server}}) * The transport gem it should have it a subset of bolt 's own gemspec depedencies (remove deps not required by bolt-transports , and should be able to be built separately from Bolt. mostly puppet / pal) * This should not break or affect Bolt's build process . * There should be a rake task to build the transport api gem. * This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo. This ticket is complete when we can run {{gem build bolt-transports}} and {{gem install bolt-transports}} to install and use the bolt-transport utillity. Questions:* What should we call the transport api gem package ? {{pe-bolt-service}}
Add Comment
This
Jira (BOLT-650) Separate bolt-transports to be it's own package
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-650 Separate bolt-transports to be it's own package Change By: Lucy Wyman Summary: [SPIKE] Separate bolt-transports to be it's own package Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-650) [SPIKE] Separate bolt-transports to be it's own package
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-650
[SPIKE] Separate bolt-transports to be it's own package
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool*and so that* I can develop an end-to-end workflow with the orchestrator client The console team needs to have the bolt-transports API be available in PE. This spike should answer: * How does bolt-transports get installed as part of PE?* The bolt transport api should live in the Bolt repository for now, preferably in it's own directory* The transport gem should have it's own gemspec, and should be able to be built separately from Bolt.* This should not break or affect Bolt's build process.* There should be a rake task to build the transport api gem. * This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo.This ticket is complete when we can run {{gem build bolt-transports}} and {{gem install bolt-transports}} to install and use the bolt-transport utillity.Questions:* What should we call the transport api gem?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-650) [SPIKE] Separate bolt-transports to be it's own package
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-650 [SPIKE] Separate bolt-transports to be it's own package Change By: Lucy Wyman Summary: [SPIKE] Separate bolt-transports to be it's own gem package Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-649) Support _run_as as an apply option
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-649 Support _run_as as an apply option Change By: Michael Smith Summary: Support run_as _run_as as an apply option Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-610) Make transport API public and allow custom transport configuration
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-610 Make transport API public and allow custom transport configuration Change By: Lucy Wyman Sprint: Bolt Kanban Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-628) Update Winston bolt ticket creation
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-628 Update Winston bolt ticket creation Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Lucy Wyman assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-630 PowerShell based tasks throw an error about a non-existant parameter Change By: Lucy Wyman Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-580) design/spike on bolt-transport api
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-580 design/spike on bolt-transport api Change By: Kate Lopresti Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-658) Validate JSON data in bolt-transport-api requests
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-658 Validate JSON data in bolt-transport-api requests Change By: Lucy Wyman *As a* bolt-transports user*I want* to know that the JSON I pass in is valid*So that* I see errors early and can fix the issueWe should validate that requirements for the JSON data received by the bolt-transport-api are met, and raise appropriate errors helpful error messages if they're not . * Verify that there are 'target' and 'task' options in the top level* Verify that target contains: * A valid host (FQDN or IP address v4 (v6?)) * password * valid username* Verify that task contains: * valid metadata content (does a function to validate this already exist?) * base64 encoded fileQuestions:* Should the password / ssh-key-content be encrypted?* Should we accept IP v6 addresses? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (BOLT-658) Validate JSON data in bolt-transport-api requests
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-658 Validate JSON data in bolt-transport-api requests Change By: Lucy Wyman *As a* bolt-transports user*I want* to know that the JSON I pass in is valid*So that* I see errors early and can fix the issue We should validate that requirements for the JSON data received by the bolt-transport-api are met, and raise appropriate errors if they're not.* Verify that there are 'target' and 'task' options in the top level* Verify that target contains:* A valid host (FQDN or IP address v4 (v6?))* password or ssh-key-content * valid user username * Verify that task contains:* valid metadata content (does a function to validate this already exist?)* File base64 encoded fileQuestions:* Should the password / ssh-key-content be encrypted?* Should we accept IP v6 addresses? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
Jira (BOLT-656) [SPIKE] Can we bypass batching and threading in the bolt executor?
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-656 [SPIKE] Can we bypass batching and threading in the bolt executor? Change By: Lucy Wyman Summary: [ SPIKE ] Can we bypass batching and threading in the bolt executor? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-652) Add basic unit tests for bolt-transports
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-652 Add basic unit tests for bolt-transports Change By: Lucy Wyman *As a* bolt-transports developer and user*I want* to be reasonably certain that changes don't break functionality*So that* I can reliably develop bolt-transports and reliably use bolt-transports There's currently no testing for the bolt- transport-api transports . We should add spec tests that verify:- That the api accepts JSON with the structure outlined in https://docs.google.com/document/d/1NGC_pVgIFm1gOOWaqMxBhbkvoyjZh3bnkYSivBQZYKc/edit#heading=h.9ke5ogmgl4w1- The api returns a bolt result object- It responds with 400 errors when required keys are not in the request payload, and contains a helpful error messageQuestions:- Is 400 the appropriate status code for missing required keys? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (BOLT-652) Add basic unit tests for bolt-transports
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-652 Add basic unit tests for bolt-transports Change By: Lucy Wyman Summary: Add basic spec unit tests for bolt- transport-api transports Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-651) Publish bolt-transports gem to internal gem mirrors
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-651 Publish bolt-transports gem to internal gem mirrors Change By: Lucy Wyman The *As a* developer for the consumer of the bolt- transport- transports api *I want* to be able to install the gem *So that* I can design and test the lifecycle management of the bolt-transports utilityThe bolt-transports gem should have it's own jenkins pipeline to be built and published to internal gem mirrors. This ticket is finished when* There's a release schedule for the gem (likely weekly releases)* A jenkins pipeline to build the gem and publish it to our internal gem mirrors* The gem can be installed from our gem mirror Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-651) Publish bolt-transports gem to internal gem mirrors
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-651 Publish bolt-transports gem to internal gem mirrors Change By: Lucy Wyman Summary: Publish bolt- transport-api transports gem to internal gem mirrors Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-650) Separate bolt-transports to be it's own gem
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-650
Separate bolt-transports to be it's own gem
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool * and so that* I can develop and an end-to-end workflow with the orchestrator client* The bolt transport api should live in the Bolt repository for now, preferably in it's own directory* The transport gem should have it's own gemspec, and should be able to be built separately from Bolt.* This should not break or affect Bolt's build process.* There should be a rake task to build the transport api gem. * This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo.This ticket is complete when we can run {{gem build bolt-transports}} and {{gem install bolt-transports}} to install and use the bolt-transport utillity.Questions:* What should we call the transport api gem?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-650) Separate bolt-transports to be it's own gem
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-650
Separate bolt-transports to be it's own gem
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool and develop and end-to-end workflow with the orchestrator client * The bolt transport api should live in the Bolt repository for now, preferably in it's own directory* The transport gem should have it's own gemspec, and should be able to be built separately from Bolt.* This should not break or affect Bolt's build process.* There should be a rake task to build the transport api gem. * This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo.This ticket is complete when we can run {{gem build bolt-transports}} and {{gem install bolt-transports}} to install and use the bolt-transport utillity.Questions:* What should we call the transport api gem?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-650) Separate bolt-transports to be it's own gem
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-650 Separate bolt-transports to be it's own gem Change By: Lucy Wyman Summary: Package transport API as Separate bolt-transports to be it's own gem Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-650) Package transport API as it's own gem
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-650
Package transport API as it's own gem
Change By:
Lucy Wyman
The *As a* bolt transport API should user*I want* to be packaged as it's own gem called ` able to install and use the bolt - transport - api `. separately from bolt*So that* I can design and test lifecycle management for the tool* The code bolt transport api should still live in the Bolt repository for now, preferably in it's own directory* The transport gem should have it's own gemspec, and should be able to be built separately from Bolt . * This should not break any workflows or pipelines around building affect Bolt's build process.* There should be a rake task to build the bolt transport api gem itself . * This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo. Questions: This ticket is complete when we can run {{gem build bolt - Is transports}} and {{gem install bolt- transport transports}} to install and use the bolt - api what transport utillity.Questions:* What should we want to call this?- Should the transport api gem have it's own directory in Bolt ? - Does it make sense for the gem to live in Bolt? Should it be it's own repo?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-663) Build bolt transport api gem
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-663
Build bolt transport api gem
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool* The bolt transport api should live in the Bolt repository for now, preferably in it's own directory* The transport gem should have it's own gemspec, and should be able to be built separately from Bolt.* This should not break or affect Bolt's build process.* There should be a rake task to build the transport api gem. * This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo.This ticket is complete when we can run {{gem build bolt-transports}} and {{gem install bolt-transports}} to install and use the bolt-transport utillity.Questions:* What should we call the transport api gem?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-663) Build bolt transport api gem
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-663
Build bolt transport api gem
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to install and use the bolt transport api separately from bolt*So that* I can design and test lifecycle management for the tool* The bolt transport api should live in the same repo as bolt Bolt repository for now , preferably in it's own directory . * The transport gem should have it's own gemspec, and should be able to be built separately from Bolt. * This should not break or affect Bolt's build process. * There should be a rake task to build the transport api gem. * This ticket doesn't include creating a pipeline ot build and publish the gem, only to make a logical home for it in the bolt repo. This ticket is complete when we can run {{gem build bolt-transports}} and {{gem install bolt-transports}} to install and use the bolt-transport utillity.Questions:* What should we call the transport api gem?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-662) Handle task parameters in transport api
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-662
Handle task parameters in transport api
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to run tasks with parameters*So that* I am not limited to running tasks that don't have parametersWe currently accept parameters in requests to the transport API, but they aren't actually applied when running the task. Tasks that read from STDIN and env vars should both work as expected. I suspect this is an issue with how we pass parameters to the { code} { executor.run_task {code } } function, but am not sure.This ticket is complete when we can run a task (the current example is 'echo') with parameters and get an appropriate response from the API indicating that the parameters were read (in this case that the 'message' param was printed to STDOUT).*Changes should be merged into the transport-serivce branch, not master*
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this
Jira (BOLT-662) Handle task parameters in transport api
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-662
Handle task parameters in transport api
Change By:
Lucy Wyman
*As a* bolt transport API user*I want* to be able to run tasks with parameters*So that* I am not limited to running tasks that don't have parametersWe currently accept parameters in requests to the transport API, but they aren't actually applied when running the task. Tasks that read from STDIN and env vars should both work as expected. I suspect this is an issue with how we pass parameters to the ` {code} executor.run_task ` {code} function, but am not sure. This ticket is complete when we can run a task (the current example is 'echo') with parameters and get an appropriate response from the API indicating that the parameters were read (in this case that the 'message' param was printed to STDOUT). *Changes should be merged into the transport-serivce branch, not master*
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this
Jira (BOLT-662) Handle task parameters in transport api
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-662 Handle task parameters in transport api Change By: Lucy Wyman * * As a* * bolt transport API user* * I want* * to be able to run tasks with parameters* * So that* * I am not limited to running tasks that don't have parametersWe currently accept parameters in requests to the transport API, but they aren't actually applied when running the task. Tasks that read from STDIN and env vars should both work as expected. I suspect this is an issue with how we pass parameters to the `executor.run_task` function, but am not sure.* * Changes should be merged into the transport-serivce branch, not master* *. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-662) Handle task parameters in transport api
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-662 Handle task parameters in transport api Change By: Lucy Wyman We **As a** bolt transport API user**I want** to be able to run tasks with parameters**So that** I am not limited to running tasks that don't have parametersWe currently read accept parameters from the request in requests to the transport api. We should read API, but they aren't actually applied when running the parameters and pass them to the task. Tasks that read from STDIN and env vars should both work as expected. I suspect this is an issue with how we pass parameters to the `executor.run_task` function, but am not sure.**Changes should be merged into the transport-serivce branch, not master**. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-662) Handle task parameters in transport api
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-662 Handle task parameters in transport api Change By: Lucy Wyman Sprint: Bolt Kanban Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-664) Add transport api support to all transports
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-664 Add transport api support to all transports Change By: Lucy Wyman Sprint: Bolt Kanban Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-663) Build bolt transport api gem
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-663 Build bolt transport api gem Change By: Lucy Wyman Sprint: Bolt Kanban Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
