Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-260 Should be easier to pass typed data on CLI Change By: Alex Dreyer It's common to want to support boolean and integer types, which currently require falling back to passing a JSON blob. We should detect the types required by a task or plan and try to coerce command-line arguments to those types when unambiguous, to avoid making people pass JSON all the time.Handling for different target types:- If String is assignable to Parse the type specified in the plan do not attempt to parse the value string as JSON .- If String is not assignable to the value successfully parses and matches the type specified attempt to parse from metadata use it as JSON and pass it on to puppet otherwise use the original string value . If it cannot be parsed raise a useful error. Test common Data types (including that Data gets a string). Also Variant[String, ...]. Optional should not error. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Josh Cooper commented on PUP-6964 Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Henrik Lindberg We will also need this functionality in order to unvendor types and providers from puppet, as previously modules didn't need to declare "module" dependencies on core T in puppet, or the loaders need to special case what were previously builtin types? 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-8549) Reduce regular expression garbage in puppet
Title: Message Title Justin Stoller updated an issue Puppet / PUP-8549 Reduce regular _expression_ garbage in puppet Change By: Justin Stoller 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-8549) Reduce regular expression garbage in puppet
Title: Message Title Justin Stoller commented on PUP-8549 Re: Reduce regular _expression_ garbage in puppet So, to summarize, we create more garbage with the original patch set, which always encodes the potential tag to UTF8, though it may not be enough to worry about. I've updated the PR to conditionally encode the potential tag if it isn't already ASCII or UTF8, since if it is ASCII or UTF8 having the regex be UTF8 works and won't trash JRuby's cache. This way we only create the additional objects on encodings where a) we know we would have already been trashing JRuby's regex cache and b) they may have raised an exception if compared against a UTF8 regex. 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-8504) Emit deprecation warning for ruby 2.1 and 2.2
Title: Message Title Josh Cooper commented on PUP-8504 Re: Emit deprecation warning for ruby 2.1 and 2.2 Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/e943a96564d74eb448505d07e7e7d217ffe61182 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-7269) SPIKE: split non-core functionality out of puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7269 SPIKE: split non-core functionality out of puppet Change By: Josh Cooper Sprint: Platform Core 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 (PUP-7582) Make attempt to export or virtualize a class an error
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7582 Make attempt to export or virtualize a class an error Change By: Josh Cooper Sub-team: Language 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-8558) Remove ability to enable non-strict mode in PMT
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8558 Remove ability to enable non-strict mode in PMT Change By: Craig Gomes Sprint: Platform Core Hopper 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-7157) Remove 'semantic' shim in Puppet 6
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7157 Remove 'semantic' shim in Puppet 6 Change By: Craig Gomes Sprint: Platform Core Hopper 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-7115) Un-vendor semantic_puppet gem for Puppet 6
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7115 Un-vendor semantic_puppet gem for Puppet 6 Change By: Craig Gomes Sprint: Platform Core Hopper 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-8504) Emit deprecation warning for ruby 2.1 and 2.2
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8504 Emit deprecation warning for ruby 2.1 and 2.2 Change By: Craig Gomes Sub-team: Coremunity Server 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-8442) type parameters do not honor when default is set to false
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8442 type parameters do not honor when default is set to false Change By: Craig Gomes Sprint: Platform Core Hopper 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 (PUP-7551) deprecate 'puppet describe'
Title: Message Title Garrett Guillotte commented on PUP-7551 Re: deprecate 'puppet describe' Josh Cooper I'm not sure whether puppet-strings uses puppet describe. Nick's references generator for the docs site doesn't appear to use it either. Henrik Lindberg copied quite a bit of 3.x documentation to 4.x/Strings docs recently, and he set this ticket to be blocked by PDOC-169, so he might have more context. 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-7582) Make attempt to export or virtualize a class an error
Title: Message Title Eric Sorenson commented on PUP-7582 Re: Make attempt to export or virtualize a class an error What is the downside of continuing the behavior as it is? Do people do this in the world right now, and if so, what problem are they trying to solve? 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-7582) Make attempt to export or virtualize a class an error
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7582 Make attempt to export or virtualize a class an error Change By: Josh Cooper Sub-team: Language 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-7582) Make attempt to export or virtualize a class an error
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7582 Make attempt to export or virtualize a class an error Change By: Craig Gomes Sub-team: Coremunity 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-7582) Make attempt to export or virtualize a class an error
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7582 Make attempt to export or virtualize a class an error Change By: Craig Gomes Sub-team: Language Coremunity 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-2973) Get rid of freeze_main
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2973 Get rid of freeze_main Change By: Josh Cooper Sub-team: Coremunity 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-6645) Remove the hiera_xxx functions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6645 Remove the hiera_xxx functions Change By: Josh Cooper Sub-team: Language 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-7601) Remove built-in LDAP Node Terminus
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7601 Remove built-in LDAP Node Terminus Change By: Josh Cooper Sub-team: Coremunity 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-1043) Remove ability to specify file checksum in `content` property
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1043 Remove ability to specify file checksum in `content` property Change By: Josh Cooper Sub-team: Coremunity 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-7551) deprecate 'puppet describe'
Title: Message Title Josh Cooper commented on PUP-7551 Re: deprecate 'puppet describe' Garrett Guillotte what work needs to be done to puppet-strings so that we don't need to use puppet describe when generating reference documentation? 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-2149) Deprecate implicit creation of symlinks when file ensure parameter is unknown
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-2149
Deprecate implicit creation of symlinks when file ensure parameter is unknown
Change By:
Eric Sorenson
This manifest creates a bogus symlink. My contention is that it should reject the invalid attribute value and not create a symlink.{code} # [eric@cloudline]~% puppet apply -e ' " file { '/tmp/jenny': ensure => symlink, } " Debug: Failed to load library 'selinux' for feature 'selinux' Notice: Compiled catalog for breve cloudline . wifi.puppetlabs.net localdomain in environment production in 0. 12 02 seconds Debug: Creating default schedulesDebug: Using settings: adding file resource 'confdir': 'File[/etc/puppet]{:path=>"/etc/puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Failed to load library 'shadow' for feature 'libshadow'Debug: Puppet::Type::User::ProviderUseradd: file useradd does not existDebug: Failed to load library 'ldap' for feature 'ldap'Debug: Puppet::Type::User::ProviderLdap: feature ldap is missingDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Puppet::Type::User::ProviderUser_role_add: file useradd does not existDebug: /User[puppet]: Provider directoryservice does not support features libuser; not managing attribute forcelocalDebug: Executing '/usr/bin/dscl . read /Users/puppet'Debug: Puppet::Type::Group::ProviderGroupadd: file groupadd does not existDebug: Failed to load library 'ldap' for feature 'ldap'Debug: Puppet::Type::Group::ProviderLdap: feature ldap is missingDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: /Group[puppet]: Provider directoryservice does not support features libuser; not managing attribute forcelocalDebug: Executing '/usr/bin/dscl -plist . -list /Groups'Debug: Executing '/usr/bin/dscl -plist . -read /Groups/puppet'Debug: Using settings: adding file resource 'vardir': 'File[/var/lib/puppet]{:path=>"/var/lib/puppet", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'logdir': 'File[/var/lib/puppet/log]{:path=>"/var/lib/puppet/log", :mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'statedir': 'File[/var/lib/puppet/state]{:path=>"/var/lib/puppet/state", :mode=>"1755", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'rundir': 'File[/var/lib/puppet/run]{:path=>"/var/lib/puppet/run", :mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'libdir': 'File[/var/lib/puppet/lib]{:path=>"/var/lib/puppet/lib", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'certdir': 'File[/etc/puppet/ssl/certs]{:path=>"/etc/puppet/ssl/certs", :mode=>"755",
Jira (PUP-5921) Deprecate source_permissions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5921 Deprecate source_permissions Change By: Josh Cooper Acceptance Criteria: We should emit a deprecation warning if anyone puts "source_permissions" in their manifests. We should not emit a deprecation warning during pluginsync (when we programmatically create a catalog with a file resource). 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-8504) Emit deprecation warning for ruby 2.1 and 2.2
Title: Message Title Patrick Carlisle assigned an issue to Patrick Carlisle Puppet / PUP-8504 Emit deprecation warning for ruby 2.1 and 2.2 Change By: Patrick Carlisle Assignee: Patrick Carlisle 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-8558) Remove ability to enable non-strict mode in PMT
Title: Message Title Josh Cooper created an issue Puppet / PUP-8558 Remove ability to enable non-strict mode in PMT Issue Type: Task Assignee: Unassigned Created: 2018/03/19 1:43 PM Fix Versions: PUP 6.0.0 Priority: Normal Reporter: Josh Cooper The PMT has a --strict-semver command line argument (defaults to true), which makes it possible to disable strict mode. This behavior is only present in our vendored semantic_puppet code. So we need to remove the capability in 6 prior to unvendoring semantic_puppet. Add Comment
Jira (PUP-7157) Remove 'semantic' shim in Puppet 6
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7157 Remove 'semantic' shim in Puppet 6 Change By: Josh Cooper Acceptance Criteria: - "semantic" shim added in PUP-7156 is removed- Make sure a newly generated module from the pdk or garethr's puppet-module-skeleton does not have the same issue described in PUP-7156. 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-7551) deprecate 'puppet describe'
Title: Message Title Josh Cooper commented on PUP-7551 Re: deprecate 'puppet describe' Putting this in needs information is the ticket it's blocked on was closed as won't do. 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-8557) Allow `notify` resource to not signal a change
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8557 Allow `notify` resource to not signal a change Change By: Henrik Lindberg Team: Platform Core 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-8492) Move the empty() function from stdlib to puppet
Title: Message Title Henrik Lindberg commented on PUP-8492 Re: Move the empty() function from stdlib to puppet Kenn Hussey It already had a release note - just that it was not flipped from "None" 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-8492) Move the empty() function from stdlib to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8492 Move the empty() function from stdlib to puppet Change By: Henrik Lindberg Release Notes: New Feature 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-8492) Move the empty() function from stdlib to puppet
Title: Message Title Kenn Hussey commented on PUP-8492 Re: Move the empty() function from stdlib to puppet Henrik Lindberg please add release notes for this issue if needed, thanks! 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-8504) Emit deprecation warning for ruby 2.1 and 2.2
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8504
Emit deprecation warning for ruby 2.1 and 2.2
Change By:
Josh Cooper
Ruby 2.1 is EOL. Ruby 2.2 will be went EOL on March 18 , 2018 . We need to bump the {{Puppet::OLDEST_RECOMMENDED_RUBY_VERSION}} to either 2. 2 or 2. 3 in preparation for Puppet 6.
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-8504) Emit deprecation warning for ruby 2.1 and 2.2
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8504 Emit deprecation warning for ruby 2.1 and 2.2 Change By: Josh Cooper Summary: Emit deprecation warning for ruby 2.1 and maybe 2.2 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-6893) Remove Ruby 1.9.3 support
Title: Message Title Patrick Carlisle assigned an issue to Patrick Carlisle Puppet / PUP-6893 Remove Ruby 1.9.3 support Change By: Patrick Carlisle Assignee: Patrick Carlisle 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-6893) Remove Ruby 1.9.3 support
Title: Message Title Patrick Carlisle assigned an issue to Unassigned Puppet / PUP-6893 Remove Ruby 1.9.3 support Change By: Patrick Carlisle Assignee: Patrick Carlisle 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-7534) Deprecate using file checksums in `content` property
Title: Message Title Josh Cooper commented on PUP-7534 Re: Deprecate using file checksums in `content` property Henrik Lindberg if a resource property behavior is being deprecated, do we typically only warn once (for all resources in the catalog)? Or do we only rely on disable_warnings? Seems like there is value in knowing about all of the locations where the issue is a problem, but because it's the file resource, it could generate lots of spam. 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-7534) Deprecate using file checksums in `content` property
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7534
Deprecate using file checksums in `content` property
Change By:
Josh Cooper
Acceptance Criteria:
The file and line number (context info) should be included in the deprecation warning.If the {{Puppet[:disable_warnings]}} puppet setting includes {{'deprecations'}}, then the warning should not be generated/displayed.
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-7534) Deprecate using file checksums in `content` property
Title: Message Title Jennifer Solman updated an issue Puppet / PUP-7534 Deprecate using file checksums in `content` property Change By: Jennifer Solman 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-7534) Deprecate using file checksums in `content` property
Title: Message Title Jennifer Solman assigned an issue to Jennifer Solman Puppet / PUP-7534 Deprecate using file checksums in `content` property Change By: Jennifer Solman Assignee: Jennifer Solman 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Eric Delaney commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Better debug information was added to 4.10.x at https://github.com/puppetlabs/puppet/commit/e45035511923ab67fa5a8ef6fa8e591f7aedf6e7 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-7584) Remove deprecated execfail method from util/execution
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7584 Remove deprecated execfail method from util/execution Change By: Josh Cooper Sub-team: Coremunity 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-7078) Remove method Puppet.newtype (deprecated since 2011)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7078 Remove method Puppet.newtype (deprecated since 2011) Change By: Josh Cooper Sub-team: Coremunity 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-7834) Change all calls to YAML.load into YAML.safe_load
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7834 Change all calls to YAML.load into YAML.safe_load Change By: Josh Cooper Sprint: Language Triage Platform Core 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-395) Document task parameter name requirements
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-395 Document task parameter name requirements Issue Type: Task Assignee: Unassigned Created: 2018/03/19 10:06 AM Priority: Normal Reporter: Alex Dreyer We don't seem to document that parameter names are constrained. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8523) Prepare release announcement (Puppet Platform 5.5.0)
Title: Message Title Kenn Hussey commented on PUP-8523 Re: Prepare release announcement (Puppet Platform 5.5.0) Garrett Guillotte do you have everything you need here? 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-394) Update puppet task spec to include multiple task implementations
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-394 Update puppet task spec to include multiple task implementations Issue Type: Task Assignee: Unassigned Created: 2018/03/19 9:49 AM Priority: Normal Reporter: Alex Dreyer 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
Jira (BOLT-393) PCP Plan
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-393 PCP Plan Issue Type: Task Assignee: Unassigned Created: 2018/03/19 9:45 AM Priority: Normal Reporter: Yasmin Rajabi As a user trying to use bolt with pcp I would like to see an example to help me get started. This could be using pcp to trigger a puppet run, having a plan that connects with ssh, winrm, and pcp, or makes use of https://github.com/maju6406/taskulator for example Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3869) Update winston (PuppetDB 5.2.1)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3869 Update winston (PuppetDB 5.2.1) Change By: Russell Mull Fix Version/s: PDB 5.2.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 (PDB-3869) Update winston (PuppetDB 5.2.1)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3869 Update winston (PuppetDB 5.2.1) Change By: Russell Mull 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-392) Application Deployment Plan
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-392 Application Deployment Plan Issue Type: Task Assignee: Unassigned Created: 2018/03/19 9:42 AM Priority: Normal Reporter: Yasmin Rajabi Many of our users update their application with a typical workflow where they need to drain connections from a load balancer, update an application, put that back into the pool, run a health check and if all succeed move on to the next set of nodes. We should have an example of this to help demonstrate how bolt can orchestrate these changes. inspiration: https://github.com/ipcrm/puppetconf-cr/blob/production/site/profile/plans/rolling_update.pp Add Comment This message was sent by
Jira (PDB-3853) Release PuppetDB 5.2.z(Platform 5.5.0 - 2018-03-14)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3853 Release PuppetDB 5.2.z(Platform 5.5.0 - 2018-03-14) Change By: Russell Mull 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 (PDB-3868) Check builds, promote to PE (PuppetDB 5.2.1)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3868 Check builds, promote to PE (PuppetDB 5.2.1) Change By: Russell Mull Fix Version/s: PDB 5.2.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 (PDB-3867) Bump versions, push directly, and tag (PuppetDB 5.2.1)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3867 Bump versions, push directly, and tag (PuppetDB 5.2.1) Change By: Russell Mull Fix Version/s: PDB 5.2.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-391) Example Plans
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-391 Example Plans Issue Type: Epic Assignee: Unassigned Created: 2018/03/19 9:40 AM Priority: Normal Reporter: Yasmin Rajabi There are many day to day workflows that our users can use Bolt to orchestrate, having examples of these common use cases will help users when writing plans for their own uses cases. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3853) Release PuppetDB 5.2.z(Platform 5.5.0 - 2018-03-14)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3853 Release PuppetDB 5.2.z(Platform 5.5.0 - 2018-03-14) Change By: Russell Mull Fix Version/s: PDB 5.2.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 (PDB-3867) Bump versions, push directly, and tag (PuppetDB 5.2.1)
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-3867 Bump versions, push directly, and tag (PuppetDB 5.2.1) Change By: Russell Mull Assignee: Zachary Kent Russell Mull 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-3865) Merge-up, branch, and create pipelines (PuppetDB 5.2.1)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3865 Merge-up, branch, and create pipelines (PuppetDB 5.2.1) Change By: Russell Mull Fix Version/s: PDB 5.2.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 (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection Change By: Josh Cooper Fix Version/s: PUP 4.10.11 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection Change By: Josh Cooper Fix Version/s: PUP 4.10.11 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-7307) Tidy should support 'purge' or update file resource
Title: Message Title Eric Delaney commented on PUP-7307 Re: Tidy should support 'purge' or update file resource Here is a comparison between the commit before this PR, and the PR. I created a used a script that created 1 or 1 either keeper files or files that would be removed by tidy. The output below is the name of the pp file which says how many keeper and loser files there are. The "runs:" line is the time from the 'Applied Catalog" message, and "average" is there average. The test ran the puppet apply which created the initial files, and then ran the same pp again for the second puppet apply. These times look fine, we appear to be slightly slower on the new code, but you can't really tell with so few files. ``` first puppet apply t_keeper1-loser1.pp prior_to_pr6699 1: runs: 3.19: 3.09: 3.17: 3.19: 3.09: average 3.1460 t_keeper1-loser1.pp pr6699 1: runs: 3.20: 3.11: 3.15: 3.12: 3.28: average 3.1720 second puppet apply t_keeper1-loser1.pp prior_to_pr6699 2: runs: 3.06: 3.52: 3.07: 3.23: 3.12: average 3.2000 t_keeper1-loser1.pp pr6699 2: runs: 3.23: 3.43: 3.43: 3.23: 3.32: average 3.3280 ``` This test is with 1 keeper and 1 files that will be removed by tidy. So with the first puppet apply (where we have to create all the initial files), we're appear to be slightly slower, but during the second puppet apply, we're faster. ``` first puppet apply t_keeper1-loser1.pp prior_to_pr6699 1: runs: 34.76: 32.44: 31.98: 32.59: 32.96: average 32.9460 t_keeper1-loser1.pp pr6699 1: runs: 37.00: 36.31: 31.04: 30.47: 32.14: average 33.3920 second puppet apply t_keeper1-loser1.pp prior_to_pr6699 2: runs: 16.30: 16.63: 16.11: 16.69: 16.94: average 16.5340 t_keeper1-loser1.pp pr6699 2: runs: 12.54: 12.21: 11.25: 11.85: 10.83: average 11.7360 ``` This test with 1 keep files and only 1 loser file to be reaped by tidy, we find that on the first puppet apply we're faster. On the second puppet apply we have 2 large puppet apply runs, I wonder if my the CPU or disk on my slice image was being used by someone else that slowed the test down? In general the times we appear to be faster. ``` first puppet apply t_keeper1-loser1.pp prior_to_pr6699 1: runs: 33.77: 32.71: 32.84: 33.64: 32.75: average 33.1420 t_keeper1-loser1.pp pr6699 1: runs: 34.57: 34.56: 31.41: 24.36: 32.90: average 31.5600 second puppet apply t_keeper1-loser1.pp prior_to_pr6699 2: runs: 11.53: 10.89: 11.43: 11.33: 11.55: average 11.3460 t_keeper1-loser1.pp pr6699 2: runs: 95.25: 92.78: 11.65: 10.99: 11.50: average 44.4340 ``` This test with 1 keeper and 1 loser files, we find that in general the proposed change is faster. ``` first puppet apply t_keeper1-loser1.pp prior_to_pr6699 1: runs: 66.20: 60.75: 62.46: 61.01: 65.91: average 63.2660 t_keeper1-loser1.pp pr6699 1: runs: 44.64: 66.19: 58.64: 59.91: 64.94: average 58.8640 second puppet apply t_keeper1-loser1.pp prior_to_pr6699 2: runs: 25.90: 26.57: 25.49: 26.33: 25.93: average 26.0440 t_keeper1-loser1.pp pr6699 2: runs: 19.79: 20.13: 20.67: 20.76: 20.37: average 20.3440 ```
Jira (PUP-8557) Allow `notify` resource to not signal a change
Title: Message Title Johnson Earls created an issue Puppet / PUP-8557 Allow `notify` resource to not signal a change Issue Type: Improvement Assignee: Unassigned Components: Types and Providers Created: 2018/03/19 9:23 AM Priority: Normal Reporter: Johnson Earls The notify resource is useful for debugging and status tracking, but becomes an issue when you have automated tooling or procedures that indicate that puppet should be re-run any time it indicates a change. Currently, the notify resource always indicates a change. This default functionality can't be changed, since there might be code that relies on that. Instead, I suggest adding a new parameter nochange which, if true, indicates the resource should not report itself as changed. I will submit a PR for this shortly. Add Comment
Jira (PUP-8442) type parameters do not honor when default is set to false
Title: Message Title Josh Cooper commented on PUP-8442 Re: type parameters do not honor when default is set to false I think we need to figure out a way to support boolean parameter/properties that doesn't break existing modules. 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-7283) Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-7283 Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization Change By: Josh Cooper Assignee: Adrien Thebo 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-2836) Incorrect lockfile placement
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-2836 Incorrect lockfile placement 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 (PUP-8289) All numeric environment names cause error on client and server
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-8289 All numeric environment names cause error on client and server Change By: Josh Cooper Assignee: J.D. 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-2983) Environment not updated via ENC if obsolete Environment in agents puppet.conf
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-2983 Environment not updated via ENC if obsolete Environment in agents puppet.conf 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 (BOLT-374) Update bolt-vanagon to ship latest platforms
Title: Message Title David Kramer assigned an issue to Nick Lewis Puppet Task Runner / BOLT-374 Update bolt-vanagon to ship latest platforms Change By: David Kramer Assignee: Nick Lewis 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-360) Store facts for targets in inventory
Title: Message Title David Kramer assigned an issue to Michal Ruzicka Puppet Task Runner / BOLT-360 Store facts for targets in inventory Change By: David Kramer Assignee: Michal Ruzicka 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-6740) sshkey: add support for "markers" / SSHCA
Title: Message Title Matthew Gyurgyik commented on PUP-6740 Re: sshkey: add support for "markers" / SSHCA We are looking at deploying ssh certificates, and the lack of support is going to force us to manage the ssh_known_hosts file with wrapper around concat. 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-8556) environment.conf modulepath should accept globs
Title: Message Title Henrik Lindberg commented on PUP-8556 Re: environment.conf modulepath should accept globs Thanks Sean Millichamp that helps a lot. 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-359) Minifact plan
Title: Message Title Michal Ruzicka assigned an issue to Michal Ruzicka Puppet Task Runner / BOLT-359 Minifact plan Change By: Michal Ruzicka Assignee: Michal Ruzicka 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.
