Jira (PUP-8290) Allow auto-conversion to Sensitive data type
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-8290
Allow auto-conversion to Sensitive data type
Issue Type:
Improvement
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Created:
2017/12/21 10:51 PM
Priority:
Normal
Reporter:
Daniel Parks
Puppet Version: 5.3.3 Puppet Server Version: N/A OS Name/Version: N/A
When passing data to a resource that declares a parameter as Sensitive the value must be manually cast to Sensitive. Please allow values matching type T to be automatically cast to values of Sensitive[T].
In particular, this would be helpful for automatic parameters.
Right now Sensitive is too much of a pain. Automatic casts would remove that cost and allow me to start using it everywhere.
Desired Behavior:
❯ puppet apply -e 'define foo ( Sensitive $p ) { } foo { "f": p => "secret" }'
Notice:
Jira (PUP-8285) filebucket --bucket behavior is either inconsistent or underexplained
Title: Message Title Garrett Guillotte commented on PUP-8285 Re: filebucket --bucket behavior is either inconsistent or underexplained I've tested and reproduced this result using puppet-agent_5.3.3.155.ge553aae-1xenial_amd64.deb built 22-Dec-2017 00:28, on a fresh Ubuntu 16.04 vmpooler VM. root@t1k1p6dk014k9pz:~# puppet filebucket --local list Error: Could not run: File not found root@t1k1p6dk014k9pz:~# puppet filebucket --local backup /etc/passwd /etc/passwd: dd47a6a4263493a9f47355ecab68b97f root@t1k1p6dk014k9pz:~# puppet filebucket --local list dd47a6a4263493a9f47355ecab68b97f 2017-12-21 16:54:43 /etc/passwd root@t1k1p6dk014k9pz:~# puppet filebucket --bucket /tmp/filebucket backup /etc/passwd /etc/passwd: dd47a6a4263493a9f47355ecab68b97f root@t1k1p6dk014k9pz:~# puppet filebucket --bucket /tmp/filebucket list
Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-3483 Systemd provider doesn't scan for changed units Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8289) All numeric environment names cause error on client and server
Title: Message Title J.D. created an issue Puppet / PUP-8289 All numeric environment names cause error on client and server Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Created: 2017/12/21 4:45 PM Priority: Normal Reporter: J.D. Puppet Version: Tested on 4.x and 5.x Puppet Server Version: tested on 4.x and 5.x OS Name/Version: All Using an all numeric environment in puppet causes the following error on the client Error: Could not initialize global default settings: undefined method `to_sym' for 8675309:Fixnum If that value is placed within quotes on the client the server returns the following error: Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Error 500 on SERVER: Server Error: undefined method `match' for 8675309:Fixnum Did you mean? catch Desired Behavior: Using an all numeric environment name complies with the regular _expression_ supplied in the documentation. Actual Behavior: All numeric ienvironment name is not functioning Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. puppet agent with --test --trace --debug Error: Could not initialize global default settings: undefined method `to_sym' for 8675309:Fixnum
Jira (PUP-8289) All numeric environment names cause error on client and server
Title: Message Title J.D. updated an issue Puppet / PUP-8289 All numeric environment names cause error on client and server Change By: J.D. *Puppet Version:*Tested on 4.x and 5.x*Puppet Server Version:*tested on 4.x and 5.x*OS Name/Version:*AllUsing an all numeric environment in puppet causes the following error on the clientError: Could not initialize global default settings: undefined method `to_sym' for 8675309:FixnumIf that value is placed within quotes on the client the server returns the following error:Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Error 500 on SERVER: Server Error: undefined method `match' for 8675309:FixnumDid you mean? catch*Desired Behavior:*Using an all numeric environment name complies with the regular _expression_ supplied in the documentation.*Actual Behavior:*All numeric ienvironment environment name is not functioningPlease take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.puppet agent with --test --trace --debugError: Could not initialize global default settings: undefined method `to_sym' for 8675309:Fixnum/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:550:in `parse_config'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:597:in `parse_config_files'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:264:in `initialize_global_settings'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:133:in `do_initialize_settings_for_run_mode'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:127:in `initialize_settings'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:67:in `block in execute'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:66:in `execute'/opt/puppetlabs/puppet/bin/puppet:5:in `' Add Comment This message was sent by Atlassian
Jira (PUP-4885) Master and Agent should not share libdir
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-4885 Master and Agent should not share libdir Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8288) Exceptions during transaction evaluate reported as success
Title: Message Title Kris Bosland created an issue Puppet / PUP-8288 Exceptions during transaction evaluate reported as success Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Kris Bosland Created: 2017/12/21 3:42 PM Fix Versions: PUP 4.10.z Priority: Major Reporter: Kris Bosland Forked off of PUP-7630, to handle only the issue that overall success is reported when an exception is not caught inside transaction.evaluate. Actually affects versions as far back as pup 4.0.0-rc1. Add Comment
Jira (BOLT-194) Gracefully handle Ctrl-C
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-194
Gracefully handle Ctrl-C
Change By:
Alex Dreyer
If bolt is interrupted while executing a plan, it may generate a large stacktrace. For example, if you enter the WinRM password incorrectly, and then Ctrl-C. We should register signal handlers and gracefully exit.{noformat}bx bolt plan run sample::single_task nodes=xcp6ifv2b4xm8e1 --modules spec/fixtures/modules -k -u Administrator -p --transport winrmPlease enter your password:^Cbundler: failed to load command: bolt (/Users/josh/work/bolt/.bundle/bin/bolt)Interrupt: /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `sleep' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `ns_wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/abstract_lockable_object.rb:43:in `ns_wait_until' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:87:in `block in wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:84:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/executor/ruby_executor_service.rb:49:in `wait_for_termination' /Users/josh/work/bolt/lib/bolt/executor.rb:39:in `on' /Users/josh/work/bolt/lib/bolt/executor.rb:57:in `run_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:72:in `run_task_instance' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:47:in `run_named_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatch.rb:60:in `invoke' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:46:in `block in call' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `call' /Users/josh/work/bolt/spec/fixtures/modules/sample/plans/single_task.pp:4:in `block in call_function' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `eval' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `block in call_function'
Jira (BOLT-194) Gracefully handle Ctrl-C
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-194
Gracefully handle Ctrl-C
Change By:
Alex Dreyer
If bolt is interrupted while executing a plan, it may generate a large stacktrace. For example, if you enter the WinRM password incorrectly, and then Ctrl-C. We should register signal handlers and gracefully exit.{noformat}bx bolt plan run sample::single_task nodes=xcp6ifv2b4xm8e1 --modules spec/fixtures/modules -k -u Administrator -p --transport winrmPlease enter your password:^Cbundler: failed to load command: bolt (/Users/josh/work/bolt/.bundle/bin/bolt)Interrupt: /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `sleep' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `ns_wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/abstract_lockable_object.rb:43:in `ns_wait_until' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:87:in `block in wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:84:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/executor/ruby_executor_service.rb:49:in `wait_for_termination' /Users/josh/work/bolt/lib/bolt/executor.rb:39:in `on' /Users/josh/work/bolt/lib/bolt/executor.rb:57:in `run_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:72:in `run_task_instance' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:47:in `run_named_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatch.rb:60:in `invoke' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:46:in `block in call' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `call' /Users/josh/work/bolt/spec/fixtures/modules/sample/plans/single_task.pp:4:in `block in call_function' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `eval' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `block in call_function'
Jira (PUP-8127) Refactor error location strings to not use words for better I18n support
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8127 Refactor error location strings to not use words for better I18n support Change By: Eric Delaney Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8286) i18n review and add decoration to cases where we raise errors as appropriate
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8286 i18n review and add decoration to cases where we raise errors as appropriate Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8286) i18n review and add decoration to cases where we raise errors as appropriate
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8286 i18n review and add decoration to cases where we raise errors as appropriate Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8122 I18n strings that include repeated lists of sentence fragments can be hard to translate Change By: Eric Delaney Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-194) Gracefully handle Ctrl-C
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-194
Gracefully handle Ctrl-C
Change By:
Alex Dreyer
If bolt is interrupted while executing a plan, it may generate a large stacktrace. For example, if you enter the WinRM password incorrectly, and then Ctrl-C. We should register signal handlers and gracefully exit.{noformat}bx bolt plan run sample::single_task nodes=xcp6ifv2b4xm8e1 --modules spec/fixtures/modules -k -u Administrator -p --transport winrmPlease enter your password:^Cbundler: failed to load command: bolt (/Users/josh/work/bolt/.bundle/bin/bolt)Interrupt: /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `sleep' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `ns_wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/abstract_lockable_object.rb:43:in `ns_wait_until' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:87:in `block in wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:84:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/executor/ruby_executor_service.rb:49:in `wait_for_termination' /Users/josh/work/bolt/lib/bolt/executor.rb:39:in `on' /Users/josh/work/bolt/lib/bolt/executor.rb:57:in `run_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:72:in `run_task_instance' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:47:in `run_named_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatch.rb:60:in `invoke' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:46:in `block in call' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `call' /Users/josh/work/bolt/spec/fixtures/modules/sample/plans/single_task.pp:4:in `block in call_function' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `eval' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `block in call_function'
Jira (BOLT-261) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-261 Uppercase class task name should not work as a reference to a task in a plan Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-194) Gracefully handle Ctrl-C
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-194
Gracefully handle Ctrl-C
Change By:
Alex Dreyer
If bolt is interrupted while executing a plan, it may generate a large stacktrace. For example, if you enter the WinRM password incorrectly, and then Ctrl-C. We should register signal handlers and gracefully exit.{noformat}bx bolt plan run sample::single_task nodes=xcp6ifv2b4xm8e1 --modules spec/fixtures/modules -k -u Administrator -p --transport winrmPlease enter your password:^Cbundler: failed to load command: bolt (/Users/josh/work/bolt/.bundle/bin/bolt)Interrupt: /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `sleep' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:43:in `ns_wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/abstract_lockable_object.rb:43:in `ns_wait_until' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:87:in `block in wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/atomic/event.rb:84:in `wait' /Users/josh/work/bolt/.bundle/gems/concurrent-ruby-1.0.5/lib/concurrent/executor/ruby_executor_service.rb:49:in `wait_for_termination' /Users/josh/work/bolt/lib/bolt/executor.rb:39:in `on' /Users/josh/work/bolt/lib/bolt/executor.rb:57:in `run_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:72:in `run_task_instance' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/loader/../../../../lib/puppet/functions/run_task.rb:47:in `run_named_task' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatch.rb:60:in `invoke' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `dispatch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:46:in `block in call' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `catch' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/functions/function.rb:45:in `call' /Users/josh/work/bolt/spec/fixtures/modules/sample/plans/single_task.pp:4:in `block in call_function' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `eval' /Users/josh/work/bolt/vendored/puppet/lib/puppet/pops/evaluator/runtime3_support.rb:307:in `block in call_function'
Jira (BOLT-261) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-261 Uppercase class task name should not work as a reference to a task in a plan Change By: Alex Dreyer Sprint: Bolt One Point Oh Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8287) I18n Review DiagnosticFormatter and DiagnosticFormatterPuppetStyle for I18n updates
Title: Message Title Eric Delaney created an issue Puppet / PUP-8287 I18n Review DiagnosticFormatter and DiagnosticFormatterPuppetStyle for I18n updates Issue Type: Task Assignee: Unassigned Created: 2017/12/21 2:19 PM Priority: Normal Reporter: Eric Delaney We need to review the used in the classes DiagnosticFormatter and DiagnosticFormatterPuppetStyle and determine if they should should be updated to support i18n or not. We should also determine if it is possible to convert DiagnosticFormatterPuppetStyle.format_location() to use Puppet::Util::Errors.error_location_with_space() so that this output will match up with the normal user output. Add Comment This message was sent by
Jira (PUP-8286) i18n review and add decoration to cases where we raise errors as appropriate
Title: Message Title
Eric Delaney created an issue
Puppet / PUP-8286
i18n review and add decoration to cases where we raise errors as appropriate
Issue Type:
Task
Assignee:
Unassigned
Created:
2017/12/21 2:14 PM
Priority:
Normal
Reporter:
Eric Delaney
There are a bunch of cases where we raise errors that we need to review and look to convert over to decorated I18N strings. Here is a good starting list of places to start looking
Puppet::ExternalFileError
Puppet::Parser::Compiler::CatalogValidationError
Puppet::DevError
Puppet::ParseError
self.fail Puppet::ParseError, detail.to_s + " on # {self}", detail * Puppet::ResourceError * Puppet::Resource::Catalog::DuplicateResourceError ** msg needs to be merged into 1 message * Puppet::Settings::PaseError * Puppet::Util::IniConfig::IniParserError * puppet/parser/resource.rb ** self.fail Puppet::ParseError, detail.to_s + " on #{self}
", detail
raise ArgumentError
Jira (PUP-8285) filebucket --bucket behavior is either inconsistent or underexplained
Title: Message Title Garrett Guillotte created an issue Puppet / PUP-8285 filebucket --bucket behavior is either inconsistent or underexplained Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 12:28 PM Priority: Normal Reporter: Garrett Guillotte Puppet Version: 5.3.3 Puppet Server Version: N/A, running agent only OS Name/Version: Ubuntu 16.04 While trying to document what puppet filebucket --bucket/-b does, I've noticed some unexpected or inconsistent behavior. If this behavior is by design, it isn't sufficiently explained in any user-facing documentation. Steps to reproduce: 1. Create a test file: touch /tmp/testfile 2. Back up the file to the local filebucket: puppet filebucket -l backup /tmp/testfile 3. Back up the same file to a filebucket on a specific path: puppet filebucket -b /tmp/testbucket backup /tmp/testfile 4. Back up a new file to that same new filebucket: touch /tmp/testfile2; puppet filebucket -b /tmp/testbucket backup /tmp/testfile2 Desired Behavior: The default local filebucket at /opt/puppetlabs/puppet/cache/bucket contains /tmp/testfile. Puppet creates a filebucket at /tmp/testbucket, and that filebucket contains /tmp/testfile and /tmp/testfile2. The documentation explains what --bucket is expected to do. Actual Behavior: The function and behavior of --bucket are not documented, so I don't know what the true expected behavior is. It is listed with the flags in the command's help text and man page, but with no context explaining what it does or is expected to do. See also PUP-5206 and PUP-5392.
Jira (PUP-4973) Different resource_type behavior between Puppet 3.x and 4.x
Title: Message Title Andrew Bogott commented on PUP-4973 Re: Different resource_type behavior between Puppet 3.x and 4.x So just to reconfirm: As of 4.x there's no longer a way to query a puppetmaster for resource-specific docs? (My UI relied on that, so this is bumming me out.) Regardless, I'd encourage you to document this endpoint as broken in the 4.x docs. I've spent a day or so trying to get it to work as documented, and I don't typically interpret "this will be removed in the next version" as "don't try to make this work in the current version because it's broken there already." Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-32) Add ability to enumerate available plans
Title: Message Title Michelle Fredette commented on BOLT-32 Re: Add ability to enumerate available plans Added to command docs and as a release note to improvements section. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-32) Add ability to enumerate available plans
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-32 Add ability to enumerate available plans Change By: Michelle Fredette Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-222) Good default error handling
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-222 Good default error handling Change By: Alex Dreyer Currenlty Currently bolt doesn't handle errors in run_* commands well. It is left to the plan author to check for errors after each run_* command actions and write error handling logic by default. Users shouldn This means that simple plans that call a series of run_* actions don 't behave as users expect.The following 'strategies' have check every action for success been discussed1 . Unless a user explicitly handles an error on any target the whole plan should exit.2. Until a user explicitly handles an error on a target that target should be skipped in future run commands.3. Bolt should ignore any node failures unless the plan explicitly checks for themHow do failures in a sub plan effect the calling plan?Should plan users be able to chose the strategy without changing the plan?What does it look like in the plan language to override the strategy?(catch different run_* invocation etc) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-271) Update Hands on Lab to use metadata features
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-271 Update Hands on Lab to use metadata features Change By: Zach Reichert Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-222) Good default error handling
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-222 Good default error handling Change By: Alex Dreyer Simple usage of Currenlty bolt doesn't handle errors in run_* commands well. It is left to the plan author to check for errors after each run_* command and write error handling logic by default. Users shouldn't have check every action for success. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-222) Good default error handling
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-222 Good default error handling Change By: Alex Dreyer Summary: Plans should fail if any tasks/command/scripts fail Good default error handling Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-222) Plans should fail if any tasks/command/scripts fail
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-222 Plans should fail if any tasks/command/scripts fail Changes to behavior here are likely to break existing plans making this a priority Change By: Alex Dreyer Sub-team: bolt Team: Direct Change Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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
Jira (BOLT-222) Plans should fail if any tasks/command/scripts fail
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-222 Plans should fail if any tasks/command/scripts fail Change By: Alex Dreyer Simple usage of Users shouldn't have check every action for success. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-259) Config file should use .yaml extension
Title: Message Title Michelle Fredette commented on BOLT-259 Re: Config file should use .yaml extension Added a new feature note. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-259) Config file should use .yaml extension
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-259 Config file should use .yaml extension Change By: Michelle Fredette Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8284) i18n need to change "on node #{node}" code to be translation friendly
Title: Message Title
Eric Delaney created an issue
Puppet / PUP-8284
i18n need to change "on node #{node}" code to be translation friendly
Issue Type:
Task
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Created:
2017/12/21 9:56 AM
Priority:
Normal
Reporter:
Eric Delaney
We need to change how we report the node that a message occurs on to be more translation friendly. Currently the common way is to say "on node # {node}". We should be more translation friendly about this. 09:42 $ grep -r 'on node' lib lib/puppet/defaults.rb: should be used on nodes running `puppet agent` or `puppet apply`. lib/puppet/error.rb: msg = "#{msg} on node #{node}
" if node lib/puppet/external/dot.rb: 'fixedsize', # default: false; label text has no affect on node size lib/puppet/parser/compiler.rb: message = "# {detail}
on node # {node.name}
" lib/puppet/util/log.rb: msg = _("% {msg}
on node % {node}
") % { msg: msg, node: node }
unless node.nil?
Jira (PUP-8283) Puppet rejects tasks with valid non-Data types like 'Hash'
Title: Message Title Alex Dreyer created an issue Puppet / PUP-8283 Puppet rejects tasks with valid non-Data types like 'Hash' Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 9:28 AM Priority: Normal Reporter: Alex Dreyer Puppet Version: Bolt Puppet Tasks can only accept parameters as JSON. However it should be valid in task metadata to use puppet types that may be assignable to JSON like bare Hash. Puppet seems to be rejecting these code Error: Failed to load metadata for task example_tasks::hash_get: Task initializer has wrong type, entry 'parameters' entry 'data' entry 'type' expects a Type[Data] value, got Type[Hash] in /Users/adreyer/src/puppetlabs/puppetconf_modules/example_tasks/tasks/hash_get.json code Desired Behavior: Task metadata that gives parameters types that may be assignable to Data should be considered valid. Actual Behavior: Puppet refuses to load tasks that use types which are not assignable to Data like Hash Add Comment
Jira (PUP-8283) Puppet rejects tasks with valid non-Data types like 'Hash'
Title: Message Title Alex Dreyer assigned an issue to Thomas Hallgren Puppet / PUP-8283 Puppet rejects tasks with valid non-Data types like 'Hash' Change By: Alex Dreyer Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-274 Remove '::init' from task names in `bolt task show *` Change By: Alex Dreyer Release Notes Summary: This is a bug fix for an unreleased feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-274 Remove '::init' from task names in `bolt task show *` Change By: Alex Dreyer Fix Version/s: BOLT 0.12.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-259) Config file should use .yaml extension
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-259 Config file should use .yaml extension Change By: Alex Dreyer Release Notes Summary: Bolt will now look for config files called `bolt.yaml` in addition to`bolt.yml` Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-267) Add ExecutionResult and Target data types
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-267 Add ExecutionResult and Target data types Change By: Alex Dreyer Fix Version/s: BOLT 0.12.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-267) Add ExecutionResult and Target data types
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-267 Add ExecutionResult and Target data types Change By: Alex Dreyer Release Notes Summary: This should not result in user facing changes Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-259) Config file should use .yaml extension
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-259 Config file should use .yaml extension Change By: Alex Dreyer Fix Version/s: BOLT 0.12.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8122 I18n strings that include repeated lists of sentence fragments can be hard to translate Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8122 I18n strings that include repeated lists of sentence fragments can be hard to translate Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8270) PAL task_signature adds 'default' to some type descriptions
Title: Message Title Henrik Lindberg commented on PUP-8270 Re: PAL task_signature adds 'default' to some type descriptions I think that makes sense. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8259) PAL list_tasks doesn't return useful results unless all task metadata is valid
Title: Message Title Henrik Lindberg commented on PUP-8259 Re: PAL list_tasks doesn't return useful results unless all task metadata is valid We could perhaps let the list_xxx return Variant[Error, TypedName], or possibly skip errors by default, but present them to the filtering lambda. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8282) amazon orders customer service phone number 1.800.290.5061 amazon customer service amazon echo customer service +AMAZON+
Title: Message Title manish sharma created an issue Puppet / PUP-8282 amazon orders customer service phone number 1.800.290.5061 amazon customer service amazon echo customer service +AMAZON+ Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 5:16 AM Environment: amazon orders customer service phone number 1.800.290.5061 amazon customer service amazon echo customer service AMAZON Priority: Normal Reporter: manish sharma https://www.eventbrite.com/e/amazon-orders-customer-service-phone-number-18002905061-amazon-customer-service-amazon-echo-tickets-41493008706 amazon orders customer service phone number 1.800.290.5061 https://www.eventbrite.com/e/amazon-orders-customer-service-phone-number-18002905061-amazon-customer-service-amazon-echo-tickets-41493008706 amazon customer service amazon echo customer service AMAZON https://www.eventbrite.com/e/amazon-orders-customer-service-phone-number-18002905061-amazon-customer-service-amazon-echo-tickets-41493008706 amazon orders customer service phone number 1.800.290.5061 https://www.eventbrite.com/e/amazon-orders-customer-service-phone-number-18002905061-amazon-customer-service-amazon-echo-tickets-41493008706 amazon customer service amazon echo customer service AMAZON
Jira (PUP-8259) PAL list_tasks doesn't return useful results unless all task metadata is valid
Title: Message Title Thomas Hallgren assigned an issue to Michael Smith Puppet / PUP-8259 PAL list_tasks doesn't return useful results unless all task metadata is valid Change By: Thomas Hallgren Assignee: Thomas Hallgren Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8253) Should be possible to separate errors from ok results in ExecutionResult without compiler
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8253 Should be possible to separate errors from ok results in ExecutionResult without compiler Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8259) PAL list_tasks doesn't return useful results unless all task metadata is valid
Title: Message Title Thomas Hallgren commented on PUP-8259 Re: PAL list_tasks doesn't return useful results unless all task metadata is valid Michael Smith do you have any thoughts on what that finer control would look like? We already pass a block to the underlying Loader#discover method (used for the optional filtering). Whatever we add here I think it should be consistent with other list_xxx methods. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8190) Move ExecutionResult and Target type into boltlib
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8190 Move ExecutionResult and Target type into boltlib Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8270) PAL task_signature adds 'default' to some type descriptions
Title: Message Title Thomas Hallgren assigned an issue to Michael Smith Puppet / PUP-8270 PAL task_signature adds 'default' to some type descriptions Change By: Thomas Hallgren Assignee: Thomas Hallgren Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8270) PAL task_signature adds 'default' to some type descriptions
Title: Message Title Thomas Hallgren commented on PUP-8270 Re: PAL task_signature adds 'default' to some type descriptions The behavior is similar for all types of ranges so when changing this we should do it consistently and leave out the default max everywhere (includes Integer, Float, Array, Callable, and Tuple). Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8281) AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact
Title: Message Title manish sharma created an issue Puppet / PUP-8281 AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 4:18 AM Environment: AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Priority: Normal Reporter: manish sharma [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT] 1_800_290_5061 HELP [https://view.joomag.com/amazon-prime-contact-1-800-290-5061- help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number- contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact] [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061
Jira (PUP-8280) 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number?
Title: Message Title manish sharma created an issue Puppet / PUP-8280 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number? Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 3:56 AM Environment: 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number? Priority: Normal Reporter: manish sharma [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT] 1_800_290_5061 HELP [https://view.joomag.com/amazon-prime-contact-1-800-290-5061- help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number- contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact] [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-
Jira (PUP-8279) 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number?
Title: Message Title manish sharma created an issue Puppet / PUP-8279 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number? Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 3:55 AM Environment: 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number? Priority: Normal Reporter: manish sharma [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT] 1_800_290_5061 HELP [https://view.joomag.com/amazon-prime-contact-1-800-290-5061- help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number- contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact] [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-
Jira (PUP-8278) AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact
Title: Message Title manish sharma created an issue Puppet / PUP-8278 AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 3:39 AM Environment: AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Priority: Normal Reporter: manish sharma [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT] 1_800_290_5061 HELP [https://view.joomag.com/amazon-prime-contact-1-800-290-5061- help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number- contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact] [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061
Jira (PUP-8277) 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number?
Title: Message Title manish sharma created an issue Puppet / PUP-8277 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number? Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 3:30 AM Environment: 1-800-270-9701 "Amazon Prime Number" 800.290.5061 Amazon Support Phone Number? Priority: Normal Reporter: manish sharma [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT] 1_800_290_5061 HELP [https://view.joomag.com/amazon-prime-contact-1-800-290-5061- help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number- contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact] [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-
Jira (PUP-8276) AMAZON PRIME CONTACT 1_8OO_29O_5O61 Amazon Prime Support Number contact
Title: Message Title manish sharma created an issue Puppet / PUP-8276 AMAZON PRIME CONTACT 1_8OO_29O_5O61 Amazon Prime Support Number contact Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 3:17 AM Environment: AMAZON PRIME CONTACT 1_8OO_29O_5O61 Amazon Prime Support Number contact Priority: Normal Reporter: manish sharma [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT] 1_800_290_5061 HELP [https://view.joomag.com/amazon-prime-contact-1-800-290-5061- help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number- contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact] [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-
Jira (PUP-8275) AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact
Title: Message Title manish sharma created an issue Puppet / PUP-8275 AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 2:38 AM Environment: AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Priority: Normal Reporter: manish sharma [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT] 1_800_290_5061 HELP [https://view.joomag.com/amazon-prime-contact-1-800-290-5061- help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number- contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact] [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061
Jira (PUP-8274) AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact
Title: Message Title manish sharma created an issue Puppet / PUP-8274 AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 2:16 AM Environment: AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Priority: Normal Reporter: manish sharma [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT] 1_800_290_5061 HELP [https://view.joomag.com/amazon-prime-contact-1-800-290-5061- help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number- contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061 [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact] [https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number- support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT] 1.8OO.29O.5061
Jira (PUP-8273) AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact
Title: Message Title manish sharma created an issue Puppet / PUP-8273 AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 2:15 AM Environment: AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Priority: Normal Reporter: manish sharma https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME CONTACT 1_800_290_5061 HELP https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 Amazon Prime Support Number contact https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061
Jira (PUP-8272) AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact
Title: Message Title manish sharma updated an issue Puppet / PUP-8272 AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Change By: manish sharma AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contactAMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contactAMAZON PRIME CONTACT 1_8OO_29O_5O61 Amazon Prime Support Number contact1-800-270-9701 "[https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Prime Number]" 800.290.5061 [https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Support Phone Number]? [https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Prime Number]" 800.290.5061 [https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Support Phone Number]? [https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Prime Number]" 800.290.5061 [https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Support Phone Number]? Microsoft Office Support 0-184-88-01-17 contacter microsoft france +CoNTACTER+ +OfficE+ +sUpPoRt+contact microsoft france 0–184–88–01–17 contacter microsoft france support microsoft france @PYAAR@ support microsoft france 0-184-88-01-17 contacter microsoft france contact microsoft france +MICROSOFT+ support microsoft france 0-184-88-01-17 contacter microsoft france contact microsoft france +CONTACTER+support microsoft france 0-184-88-01-17 contacter microsoft france contact microsoft france +CONTACTER+support microsoft france 0-184-88-01-17 contacter microsoft france contact microsoft france @SUPPORT@0-184-88-01-17 support de windows Microsoft Office Support +MIROSOFT+ +OFFICE+ +SUPPORT+microsoft service client 0-184-88-01-17 contacter microsoft par mail +SERVICE+ +CLIENT+ Microsoft Office Support 0-184-88-01-17 support de windows +SUPPORT+ +DE+ +WINDOWS+service client Microsoft 0-184-88-01-17 contact microsoft +MICROSOFT+contact microsoft 0-184-88-01-17 contacter microsoft CONATCT+MICROSOFT ‘microsoft téléphone 0-184-88-01-17 contact microsoft +TELEPHONE+Microsoft Office Support 0-184-88-01-17 support de windows +SUPPORT+ contacter microsoft france 0-184-88-01-17support microsoft france contact microsoft france +FRANCE+support microsoft france 0-184-88-01-17 contacter microsoft france contact microsoft france +CONTACTER+ [AMAZON PRIME CONTACT |https:// webcache.googleusercontent.com/search?q=cache:YBLaUCeIRFIJ:https:// view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883 +=1=en=clnk=in ] 1_800_290_5061 [ HELP AMAZON PRIME NUMBER SUPPORT|https://webcache.googleusercontent.com/search?q=cache:YBLaUCeIRFIJ:https://view.joomag.com/amazon-prime-contact-1-800-290-5061-help-amazon-prime-number-support-18oo29o5061-amazon-prime-support-number-contact/0518989001509019883+=1=en=clnk=in] 1.8OO.29O.5061 [ Amazon Prime Support Number
Jira (PUP-8272) AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact
Title: Message Title manish sharma created an issue Puppet / PUP-8272 AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Issue Type: Bug Assignee: Unassigned Created: 2017/12/21 2:04 AM Environment: AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact Priority: Normal Reporter: manish sharma AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact AMAZON PRIME CONTACT 1_800_290_5061 HELP AMAZON PRIME NUMBER SUPPORT 1.8OO.29O.5061 Amazon Prime Support Number contact AMAZON PRIME CONTACT 1_8OO_29O_5O61 Amazon Prime Support Number contact 1-800-270-9701 "https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Prime Number" 800.290.5061 https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Support Phone Number? https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Prime Number" 800.290.5061 https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Support Phone Number? https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Prime Number" 800.290.5061 https://www.facebook.com/business/help/community/question/?id=964706123682282 Amazon Support Phone Number? Microsoft Office Support 0-184-88-01-17 contacter microsoft france CoNTACTER
Jira (PUP-8270) PAL task_signature adds 'default' to some type descriptions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8270 PAL task_signature adds 'default' to some type descriptions Change By: Henrik Lindberg Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8270) PAL task_signature adds 'default' to some type descriptions
Title: Message Title Henrik Lindberg commented on PUP-8270 Re: PAL task_signature adds 'default' to some type descriptions String[1, default] has expanded the max number of chars. I think it should skip showing that - just like a String[default, default] is not generated for String. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title Henrik Lindberg commented on PUP-8271 Re: init plans in bolt do not load correctly from 'bolt plan show' Fix merged to master. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8271 init plans in bolt do not load correctly from 'bolt plan show' Change By: Henrik Lindberg Release Notes Summary: release note not needed for puppet - this only affects Bolt. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8271 init plans in bolt do not load correctly from 'bolt plan show' Change By: Henrik Lindberg Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
