Jira (BOLT-1118) Add a command that lists available modules and their versions
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1118 Add a command that lists available modules and their versions Change By: Cas Donoghue Labels: BOLT-next 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-1118) Add a command that lists available modules and their versions
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1118 Add a command that lists available modules and their versions Change By: Cas Donoghue Fix Version/s: BOLT Next 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-1108) Add site-modules to the module path for bolt
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1108 Add site-modules to the module path for bolt Change By: Cas Donoghue Fix Version/s: BOLT Next 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-1108) Add site-modules to the module path for bolt
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1108 Add site-modules to the module path for bolt Change By: Cas Donoghue Labels: BOLT-next 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-1108) Add site-modules to the module path for bolt
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1108 Add site-modules to the module path for bolt Change By: Cas Donoghue Release Notes Summary: According to an updated convention `site-modules` is now recommended to be used instead of `site` for any modules not intended to be managed with a Puppetfile. Both `site` and `site-modules` are now included on the default modulepath to maintain backward compatibility and support the new convention. Release Notes: Enhancement 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-1118) Add a command that lists available modules and their versions
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1118 Add a command that lists available modules and their versions Change By: Cas Donoghue Labels: BOLT-next 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-1108) Add site-modules to the module path for bolt
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1108 Add site-modules to the module path for bolt Change By: Cas Donoghue Labels: BOLT-next 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-1131) TaskMissing error message is cryptic
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1131 TaskMissing error message is cryptic Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1876) Provide better documentation on structured executable facts
Title: Message Title Nate McCurdy commented on FACT-1876 Re: Provide better documentation on structured executable facts Big +1 to this ticket. Some simple examples of using BASH/Powershell to output arrays, hashes, and booleans would be good. Could start with simply documenting the tests used in Facter's acceptances tests: https://github.com/puppetlabs/facter/blob/master/acceptance/tests/external_facts/structured_executable_facts.rb 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-9456) Create SSLContext and SSLProvider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9456 Create SSLContext and SSLProvider Change By: Josh Cooper Fix Version/s: PUP 6.y Fix Version/s: PUP 6.4.0 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-9457) Add HttpPool method for creating connections using an SSLContext
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9457 Add HttpPool method for creating connections using an SSLContext Change By: Josh Cooper Sprint: 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 (PUP-9503) Baseline pipeline time improvement targets for testing changes
Title: Message Title Jonathan Morris commented on PUP-9503 Re: Baseline pipeline time improvement targets for testing changes Unfortunately, there is no easy way to guesstimate this, as it all runtime data driven. Since we don't know how many tests we'd be pulling, we have no baseline for the math for even a simple approximation. Classic chicken and egg type problem. We might be able to provide how much time was spent on a per directory basis in a given acceptance (sub)suite. Would that be helpful? If so, be happy to do further research. 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-9504) Bundled augeas fails to parse CentOS 7.6 default /etc/sudoers
Title: Message Title
Ryan White updated an issue
Puppet / PUP-9504
Bundled augeas fails to parse CentOS 7.6 default /etc/sudoers
Change By:
Ryan White
During a puppet run, on CentOS 7.6 hosts, a warning appears:{code:java} Warning: Augeas[sudo/requiretty](provider=augeas): Loading failed for one or more files, see debug for /augeas//erroroutput{code}The relevant excerpt from augtool is{code:java} $ /opt/puppetlabs/puppet/bin/augtool errors...Error in /etc/sudoers:73.12 (parse_failed) Iterated lens matched less than it should Lens: /opt/puppetlabs/puppet/share/augeas/lenses/dist/sudoers.aug:537.10-.70:Last matched: /opt/puppetlabs/puppet/share/augeas/lenses/dist/sep.aug:47.18-.40:Next (no match): /opt/puppetlabs/puppet/share/augeas/lenses/dist/sudoers.aug:419.23-420.57: {code}Line 73, col 12 is `always_query_group_plugin`:{code:java} $ nl -b a /etc/sudoers67 # Prior to version 1.8.15, groups listed in sudoers that were not68 # found in the system group database were passed to the group69 # plugin, if any. Starting with 1.8.15, only groups of the form70 # %:group are resolved via the group plugin by default.71 # We enable always_query_group_plugin to restore old behavior.72 # Disable this option for new behavior.73 Defaultsalways_query_group_plugin74 {code}This appears to be the same issue described at [https://bugzilla.redhat.com/show_bug.cgi?id=1649287] which is patched upstream: [https://github.com/hercules-team/augeas/pull/588/files], but not yet released.It looks like some other patches are applied to the vendored augeas ([https://github.com/puppetlabs/puppet-runtime/tree/1838c5c9e29923a0eb1042a8fbbf39ad838006d2/resources/patches/augeas] ), but it wasn't obvious how to test my patch by building an AIO RPM locally if I were to submit a PR.
Add Comment
Jira (PUP-9504) Bundled augeas fails to parse CentOS 7.6 default /etc/sudoers
Title: Message Title Ryan White created an issue Puppet / PUP-9504 Bundled augeas fails to parse CentOS 7.6 default /etc/sudoers Issue Type: Bug Affects Versions: PUP 6.2.0, PUP 5.5.10 Assignee: Unassigned Components: AIO Created: 2019/02/19 2:21 PM Environment: OS: CentOS 7.6 Puppet Agent AIO 5.5.10, 6.2.0 sudo-1.8.23-3.el7.x86_64 I would guess it should be possible to reproduce with a plain CentOS 7.6 VM, but I haven't tried. The issue does affect a couple servers I have laying around in a dev environment. Priority: Normal Reporter: Ryan White During a puppet run, on CentOS 7.6 hosts, a warning appears: Warning: Augeas[sudo/requiretty](provider=augeas): Loading failed for one or more files, see debug for /augeas//error output The relevant excerpt from augtool is
Jira (PDB-4266) Make package inventory actually sync
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4266 Make package inventory actually sync Change By: Austin Blatt Summary: A subset of facts is synced every time Make package inventory actually sync runs 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-1108) Add site-modules to the module path for bolt
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1108 Add site-modules to the module path for bolt Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4269) Integer comparisons in PQL can overflow the Java int type
Title: Message Title Robert Roland commented on PDB-4269 Re: Integer comparisons in PQL can overflow the Java int type The bug is in transform.clj - should be using Long. instead of Integer. in transform-integer function. Puppet docs say the Integer datatype holds 64-bit integers: https://puppet.com/docs/puppet/5.3/lang_data_number.html#the-integer-data-type 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-4269) Integer comparisons in PQL can overflow the Java int type
Title: Message Title
Adrian Parreiras Horta created an issue
PuppetDB / PDB-4269
Integer comparisons in PQL can overflow the Java int type
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/02/19 1:42 PM
Labels:
maintenance
Priority:
Normal
Reporter:
Adrian Parreiras Horta
In the entity part of a PQL query, it is possible to use a value that overflows an unsigned Java int, specifically 2,147,483,647. For example:
puppet query 'fact_contents[] {path ~> ["mountpoints", "/", "available_bytes"] and value < 2147483648}'
Error response 400 Bad Request from server: For input string: "2147483648"
Turning on debug level logging will reveal an exception in puppetdb.log
java.lang.NumberFormatException: For input string: "2147483648"
Jira (PUP-9482) add index function to return index/key in array/hash/string and other iterables
Title: Message Title Jean Bond updated an issue Puppet / PUP-9482 add index function to return index/key in array/hash/string and other iterables Change By: Jean Bond Labels: resolved-issue-added 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-9467) Type validation fails when there is no type - needs human-readable error message
Title: Message Title Jean Bond commented on PUP-9467 Re: Type validation fails when there is no type - needs human-readable error message This is marked with fixversions of 5.5.11 and 6.3.0; is this going into 6.0.6 as well? 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-9372) Add collection operations to Puppet core
Title: Message Title Jean Bond updated an issue Puppet / PUP-9372 Add collection operations to Puppet core Change By: Jean Bond Labels: resolved-issue-added 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-9497) Deprecate fine grained file and environment timeouts
Title: Message Title Rob Braden updated an issue Puppet / PUP-9497 Deprecate fine grained file and environment timeouts Change By: Rob Braden Team: 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-9498) Calling hiera first nullifies lookup_options.
Title: Message Title Rob Braden updated an issue Puppet / PUP-9498 Calling hiera first nullifies lookup_options. Change By: Rob Braden Team: 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-9503) Baseline pipeline time improvement targets for testing changes
Title: Message Title Rob Braden updated an issue Puppet / PUP-9503 Baseline pipeline time improvement targets for testing changes Change By: Rob Braden Team: Coremunity Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9503) Baseline pipeline time improvement targets for testing changes
Title: Message Title Rob Braden updated an issue Puppet / PUP-9503 Baseline pipeline time improvement targets for testing changes Change By: Rob Braden 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-9503) Baseline pipeline time improvement targets for testing changes
Title: Message Title Melissa Stone commented on PUP-9503 Re: Baseline pipeline time improvement targets for testing changes Jonathan Morris would you be able to get any estimates around this? It'll help as we prioritize this work. Mostly what we need are baseline estimates on how much time we'll save by making these changes in our ci pipeline. Is that something you might be able to get a feel for? 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-9503) Baseline pipeline time improvement targets for testing changes
Title: Message Title Melissa Stone created an issue Puppet / PUP-9503 Baseline pipeline time improvement targets for testing changes Issue Type: Task Assignee: Unassigned Created: 2019/02/19 11:30 AM Priority: Normal Reporter: Melissa Stone 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 a
Jira (PUP-9468) The low-level netcode stuff, to change default server selection to use server instead of the first entry of server_list when failover has not happened.
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9468 The low-level netcode stuff, to change default server selection to use server instead of the first entry of server_list when failover has not happened. Change By: Melissa Stone Sprint: Platform Core Coremunity 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-9336) Ensure provider suitability is always lazily evaluated
Title: Message Title Jean Bond updated an issue Puppet / PUP-9336 Ensure provider suitability is always lazily evaluated Change By: Jean Bond Labels: resolved-issue-added 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-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title Jean Bond updated an issue Puppet / PUP-9324 Puppet agent run output to differentiate between corrective and intentional change Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4039) package resource doesn't find new packages in yum repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4039 package resource doesn't find new packages in yum repo Change By: Geoff Nichols Labels: community linux package redhat triaged type_and_provider yum Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1888) 'os.release' values not correct for VZ7
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1888 'os.release' values not correct for VZ7 Change By: Geoff Nichols Team: Platform OS Puppet Romania 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-9479) "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-9479 "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions. Change By: Geoff Nichols Team: Platform OS Puppet Romania 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-9479) "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-9479 "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions. Change By: Geoff Nichols Labels: needs_repro permissions type_and_provider windows 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-9479) "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-9479 "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions. Change By: Geoff Nichols Sprint: PR - Triage 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-9494) Update HA Documentation on enabling a replica
Title: Message Title Kenn Hussey commented on PUP-9494 Re: Update HA Documentation on enabling a replica Thanks Melissa Stone. At this point we're not planning for a 6.3.1 but we'll see. 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-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Geoff Nichols Assignee: Geoff Nichols 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-9494) Update HA Documentation on enabling a replica
Title: Message Title Melissa Stone commented on PUP-9494 Re: Update HA Documentation on enabling a replica Thanks Kenn Hussey. This ticket is tied to https://tickets.puppetlabs.com/browse/PUP-9025, which did not make it into 6.3.0. I just set it to target PUP 6.y, because I'm not sure where it'll land, if there's going to be a 6.3.z or if it'll go straight to 6.4.0 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-9025) Filebucket resources fail when using server_list
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9025 Filebucket resources fail when using server_list Change By: Melissa Stone Fix Version/s: PUP 6.3.0 Fix Version/s: PUP 6.y 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-9494) Update HA Documentation on enabling a replica
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9494 Update HA Documentation on enabling a replica Change By: Melissa Stone Fix Version/s: PUP 6.4.0 Fix Version/s: PUP 6.y 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-9494) Update HA Documentation on enabling a replica
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9494 Update HA Documentation on enabling a replica Change By: Melissa Stone Fix Version/s: PUP 6.3.0 Fix Version/s: PUP 6.4.0 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-9494) Update HA Documentation on enabling a replica
Title: Message Title Kenn Hussey commented on PUP-9494 Re: Update HA Documentation on enabling a replica Melissa Stone I think this should probably target 6.4 instead of 6.3 (unless it's actually going out with tomorrow's release). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4266) A subset of facts is synced every time sync runs
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4266
A subset of facts is synced every time sync runs
Change By:
Austin Blatt
In pe-puppetdb the {{:package_inventory}} "fact" is included in the fact data when its hash is generated but package information is then stored and queried on its own. The result is that if a fact needs to be synced to another PuppetDB, the package inventory will not be synced and the resulting fact hash will be different between the PuppetDBs. Then roughly ~50% of those factsets with mismatched hashes will sync every sync run. This was seen in a customers infrastructure in PDB-4072 as the HA being out of sync after a restart because while the primary PuppetDB was down facts were still being submitted to the secondary PuppetDB, so when the primary came back online it synced those facts and generated the wrong hash.
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 "
Jira (PDB-4266) A subset of facts is synced every time sync runs
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4266
A subset of facts is synced every time sync runs
Change By:
Austin Blatt
In pe-puppetdb the {{:package_inventory}} "fact" is included in the fact data when its hash is generated but package information is then stored and queried on its own. The result is that if a fact needs to be synced to another PuppetDB, the package inventory will not be synced and the resulting fact hash will be different between the PuppetDBs. Then roughly ~50% of those disjoint factsets with mismatched hashes will sync every sync run.
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
Jira (PDB-4266) A subset of facts is synced every time sync runs
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4266
A subset of facts is synced every time sync runs
Change By:
Austin Blatt
In pe-puppetdb the {{:package_inventory}} "fact" is included in the fact data when its hash is generated but package information is then stored and queried on its own. The result is that if a fact needs to be synced to another PuppetDB, the package inventory will not be synced and the resulting fact hash will be different between the PuppetDBs. Then roughly ~50% of those disjoint
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-4266) A subset of facts is synced every time sync runs
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4266
A subset of facts is synced every time sync runs
Change By:
Austin Blatt
In pe-puppetdb the {{:package_inventory}} "fact" is included in the fact data when its hash is generated but package information is then stored and queried on its own. The result is that if a fact needs to be synced to another PuppetDB, the package inventory will not be synced and the resulting fact hash will be
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-4266) A subset of facts is synced every time sync runs
Title: Message Title Austin Blatt commented on PDB-4266 Re: A subset of facts is synced every time sync runs Work done to add the package inventory to PE did not properly adjust the HA sync code to sync packages. 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-1053) ruby task helper symbolized top level parameter key but no others.
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1053 ruby task helper symbolized top level parameter key but no others. Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1131) TaskMissing error message is cryptic
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1131
TaskMissing error message is cryptic
Change By:
Alex Dreyer
*Puppet Version:* 6.xUsing plan functions from manifest code generates a cryptic error message about the bolt library.*Desired Behavior:*The error message should be something close to"Plan language function #{action} cannot be used from declaritive manifest code or apply blocks"Examples:bolt apply -e "run_task(foo,bar)" Question: Is there a good There is no reason for to use the Puppet error message anymore the {{run_}} functions should generate this message to be generated directly when called from puppet now that compilation during an {{apply}}When this work is released we should ticket removing the functions are not part error messages from a future version of puppet ? Answer: No .
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.
T
Jira (BOLT-1131) TaskMissing error message is cryptic
Title: Message Title Alex Dreyer moved an issue Puppet Task Runner / BOLT-1131 TaskMissing error message is cryptic Change By: Alex Dreyer Key: PUP BOLT - 9475 1131 Project: Puppet Task Runner 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-1131) TaskMissing error message is cryptic
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1131 TaskMissing error message is cryptic Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9475) TaskMissing error message is cryptic
Title: Message Title
David Kramer updated an issue
Puppet / PUP-9475
TaskMissing error message is cryptic
Change By:
David Kramer
*Puppet Version:* 6.xUsing plan functions from manifest code generates a cryptic error message about the bolt library.*Desired Behavior:*The error message should be something close to"Plan language function #{action} cannot be used from declaritive manifest code or apply blocks"Examples:bolt apply -e "run_task(foo,bar)"Question: Is there a good reason for this message to be generated from puppet now that the functions are not part of puppet? Answer: No.
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
Jira (BOLT-1106) Upgrade to r10k version 3 for pdk compatibility
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1106 Upgrade to r10k version 3 for pdk compatibility Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9457) Add HttpPool method for creating connections using an SSLContext
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9457 Add HttpPool method for creating connections using an SSLContext Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1125) Add info about what was run to Result or ResultSet
Title: Message Title Alex Dreyer commented on BOLT-1125 Re: Add info about what was run to Result or ResultSet Chris Barker Is the proposal above enough to solve your problem? 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-1052) Support run-as for shell localhost transport.
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1052 Support run-as for shell localhost transport. Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title David Kramer assigned an issue to Nick Lewis Puppet Task Runner / BOLT-901 Improve Plan Logging with apply 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-901) Improve Plan Logging with apply
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Alex Dreyer
ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.SolutionWhen the format is human and plan_logging is active every run action should trigger the same output it would if the action was run on it's own from the CLI.* {{plan_logging}}: is only part of the human format and plan logging messages are printed on stdout not stderr* info level logging is primarily about logging full input/output of each action from a plan. * notice level logging is only used initially with the {{notice}} function from plans.* {{plan_logging}} messages should be indented to make it easier to scan* Individual node results should be output as part of plan logging when there are fewer than {{n}} targets for an action.Questions:* How can we show human readable verbose apply output(ie event logs from an apply report)?* Do we need to expose access to print human readable messages to stdout as a plan function or is {{notice}} enough? (defer and build if needed)* Do we need to show progress of actions when the format is json? (not initially defer and build later if needed)* Do we need an option for the bolt user (rather then the author) to suppress individual node results from the human format?(defer and build later if needed)* How will this work with BoltSpec? (defer and build later if needed. pass a noop outputter to executor for now)Possible short term fix fixes :* add new formatter "verbose-human". verbose human output should print full results from actions during a plan run. * clean up output from {{apply_prep}} and {{apply}} so they only logs a single result for each target.
Add Comment
Jira (BOLT-1130) Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-1130 Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params Change By: Ethan Brown Release Notes Summary: The PowerShell cmdlet ConvertTo-Json typically does not produce JSON output consumable by the --params Bolt argument. Some values may need additional escaping to be properly passed to Bolt, while other types of values may not serialize in an easily consumable way. The PowerShell stop-parsing symbol --% may be used in some cases to address the escaping problem. A more comprehensive general solution will be addressed later. Release Notes: Known Issue 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.co
Jira (BOLT-724) Ability to specify Puppetfile in config and CLI
Title: Message Title Adam Buxton commented on BOLT-724 Re: Ability to specify Puppetfile in config and CLI That being the case I believe it is definitely down to clarity of how and what is copied to the agents. I'll admit my understanding was the module is copied/deployed to the agent (not just the required subset of it) hence the need for a Puppetfile. I believe the discussion is similar to discussions on subsets of Puppet code for masterless Puppet, but crosses the realms of how to make it self service? How do I give the siloed org in the NOC access to just the modules they need to be able to run Puppet apply and redeploy the server of application role::X when i don't want to give them access to the full control_repo. I think some of this may be down to "what is a bolt project repo" and "how is that not just a control_repo with a bolt.yaml"? On the packaging subject, the discussion I was part of during Bolts initial release was how could we use this to execute against localhost and package scripts or indeed Puppetcode with it to run against the node itself, similar to how Gitlab is deployed. 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-1087) Create new boltdir docs page
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1087 Create new boltdir docs page Change By: David Kramer Assignee: 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 this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1118) Add a command that lists available modules and their versions
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1118 Add a command that lists available modules and their versions Change By: David Kramer Assignee: 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 this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-159) Bolt commands on Powershell require triple quoting
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-159 Bolt commands on Powershell require triple quoting Change By: David Kramer Fix Version/s: BOLT Next 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-724) Ability to specify Puppetfile in config and CLI
Title: Message Title Alex Dreyer commented on BOLT-724 Re: Ability to specify Puppetfile in config and CLI Modules are not deployed on remote targets for bolt apply. The catalog is compiled locally on the controller node so hiera data and manifests never leave the the controller. Bolt then copies the parts of the module needed to exectute the catalog to the target similar to how the agent does a pluginsync(but bolt also includes /files). Sharing bolt code and using different code in different circumstances is the goal behind having bolt read code from the bolt project repo rather then a single hard coded location like puppet. Our current story for bolt as an application deployment tool is to keep a specific repository of bolt code for the application either by creating a Boltdir directory inside the application repo or creating a new repo with an bolt.yaml file at the top level. I don't think we've 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-724) Ability to specify Puppetfile in config and CLI
Title: Message Title Adam Buxton commented on BOLT-724 Re: Ability to specify Puppetfile in config and CLI I believe the idea/discussion was that Puppet apply requires the modules deploying on the agent as well as the workstation. Based on that and this may be due to lack of clarity on just exactly how Apply tasks work, the user wanted to be able to specify which Puppetfile to use so that profiles of certain modules can be used in conjunction with each other and the modulepath flag, but not expose every module to the agents. I believe the driving force was not to give everyone git checkout rights to the control_repo but be able to provide packages of a slimmed down control repo and be able to use the --Puppetfile flag to control modules deployed on remote agents while all are deployed on the local workstation. I've seen similar discussions several times in the community and at events on how Bolt could be used as a application deployment tool if it had feature xyz, including a discussion on bolt as a dependency of a package. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9487) Prepare release announcement (Puppet Platform 6.3.0)
Title: Message Title Kenn Hussey commented on PUP-9487 Re: Prepare release announcement (Puppet Platform 6.3.0) Eric Sorenson please provide a draft for review today, if possible, 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 (BOLT-724) Ability to specify Puppetfile in config and CLI
Title: Message Title Alex Dreyer commented on BOLT-724 Re: Ability to specify Puppetfile in config and CLI [~adam buxton] can you go into more detail about "segregating puppet apply tasks". Why doesn't bolt just work with git [control repo] branch checkouts? When using `bolt` with your control repo you should put `bolt.yaml in the root of the control repo. The Puppetfile should then be discovered automatically from anywhere in the control repo. My concern with having a `-puppetfile` option is that bolt does not install modules relative to the `Puppetfile` but into it's configured modulepath which by default means `modules` in the bolt project dir. If you pass `-puppetfile` you will likely wipe out modules in the project and then have to remember to reinstall the correct ones later. I don't see any problem with a `puppetfile` config option but I'm not sure I've heard a solid use case for having one. 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-1130) Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params
Title: Message Title
Ethan Brown updated an issue
Puppet Task Runner / BOLT-1130
Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params
Change By:
Ethan Brown
BOLT-159 introduced a change to simplify argument passing from PowerShell when dealing with nested quotes.The change does improve the case mentioned, such that users can now use a simpler invocation like the following (rather than using {{"""}} themselves): {code} bolt command run 'echo "hi from $(hostname)"' --modulepath . --nodes winrm://localhost -u Administrator -p Qu@lity! --no-ssl{code} However, there are still cases where using more complex argument passing does not work properly due to not all values being escaped correctly for Ruby.In an ideal situation, a complex object should be serializable to a JSON string, which can then be passed directly like {{--params ($myobject | ConvertTo-Json)}}. Note that we will likely need a new PowerShell helper to serialize the values as desired, because of the way {{ConvertTo-Json}} handles certain types. For instance, more complex values like {{RegEx}}, {{IO.FileInfo}} and {{DateTime}} do not serialize in a way that's friendly to Bolt, requiring that {{ToString()}} be called first. {code} PS C:\cygwin64\home\Administrator> [DateTime]::Now | ConvertTo-Json{"value": "\/Date(155054351)\/","DateTime": "Tuesday, February 19, 2019 3:08:04 PM"}PS C:\cygwin64\home\Administrator> [DateTime]::Now.ToString() | ConvertTo-Json"2/19/2019 3:08:07 PM"PS C:\cygwin64\home\Administrator> [IO.FileInfo]'c:\windows' | ConvertTo-Json{"Name": "windows","Length": null,"DirectoryName": "c:\\","Directory": { "Name": "c:\\", "FullName": "c:\\", "Parent": null, "Exists": true, "Root": { "Name": "c:\\", "FullName": "c:\\", "Parent": null, "Exists": true, "Root": "c:\\", "Extension": "", "CreationTime": "\/Date(1536991766317)\/", "CreationTimeUtc": "\/Date(1536991766317)\/", "LastAccessTime": "\/Date(1550181187575)\/", "LastAccessTimeUtc": "\/Date(1550181187575)\/", "LastWriteTime": "\/Date(1550181186731)\/", "LastWriteTimeUtc": "\/Date(1550181186731)\/", "Attributes": 22 }, "Extension": "", "CreationTime": "\/Date(1536991766317)\/", "CreationTimeUtc": "\/Date(1536991766317)\/", "LastAccessTime": "\/Date(1550181187575)\/", "LastAccessTimeUtc": "\/Date(1550181187575)\/", "LastWriteTime": "\/Date(1550181186731)\/", "LastWriteTimeUtc": "\/Date(1550181186731)\/", "Attributes": 22
Jira (BOLT-159) Bolt commands on Powershell require triple quoting
Title: Message Title Ethan Brown commented on BOLT-159 Re: Bolt commands on Powershell require triple quoting Merged into master as https://github.com/puppetlabs/bolt-vanagon/commit/ae57a50ea979077b34493785967fc44bbd627f3a 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-1130) Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params
Title: Message Title
Ethan Brown updated an issue
Puppet Task Runner / BOLT-1130
Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params
Change By:
Ethan Brown
BOLT-159 introduced a change to simplify argument passing from PowerShell when dealing with nested quotes.The change does improve the case mentioned, such that users can now use a simpler invocation like the following (rather than using {{"""}} themselves):{code}bolt command run 'echo "hi from $(hostname)"' --modulepath . --nodes winrm://localhost -u Administrator -p Qu@lity! --no-ssl{code}However, there are still cases where using more complex argument passing does not work properly due to not all values being escaped correctly for Ruby.In an ideal situation, a complex object should be serializable to a JSON string, which can then be passed directly like {{--params ($myobject | ConvertTo-Json)}}. Note that we will likely need a new PowerShell helper to serialize the values as desired, because of the way {{ConvertTo-Json}} handles certain types. For instance, more complex values like {{RegEx}}, {{IO.FileInfo}} and {{DateTime}} do not serialize in a way that's friendly to Bolt, requiring that {{ToString()}} be called first.{code}PS C:\cygwin64\home\Administrator> [DateTime]::Now | ConvertTo-Json{"value": "\/Date(155054351)\/","DateTime": "Tuesday, February 19, 2019 3:08:04 PM"}PS C:\cygwin64\home\Administrator> [DateTime]::Now.ToString() | ConvertTo-Json"2/19/2019 3:08:07 PM"PS C:\cygwin64\home\Administrator> [IO.FileInfo]'c:\windows' | ConvertTo-Json{"Name": "windows","Length": null,"DirectoryName": "c:\\","Directory": { "Name": "c:\\", "FullName": "c:\\", "Parent": null, "Exists": true, "Root": { "Name": "c:\\", "FullName": "c:\\", "Parent": null, "Exists": true, "Root": "c:\\", "Extension": "", "CreationTime": "\/Date(1536991766317)\/", "CreationTimeUtc": "\/Date(1536991766317)\/", "LastAccessTime": "\/Date(1550181187575)\/", "LastAccessTimeUtc": "\/Date(1550181187575)\/", "LastWriteTime": "\/Date(1550181186731)\/", "LastWriteTimeUtc": "\/Date(1550181186731)\/", "Attributes": 22 }, "Extension": "", "CreationTime": "\/Date(1536991766317)\/", "CreationTimeUtc": "\/Date(1536991766317)\/", "LastAccessTime": "\/Date(1550181187575)\/", "LastAccessTimeUtc": "\/Date(1550181187575)\/", "LastWriteTime": "\/Date(1550181186731)\/", "LastWriteTimeUtc": "\/Date(1550181186731)\/", "Attributes": 22
Jira (BOLT-159) Bolt commands on Powershell require triple quoting
Title: Message Title Ethan Brown commented on BOLT-159 Re: Bolt commands on Powershell require triple quoting The following comment was left on PR describing what's improved: While this is not a complete solution to more complex argument passing with --params (new BOLT ticket filed as BOLT-1130), for the more trivial cases where additional escaping is not required, this moves the ball forward. Given the command bolt command run 'echo "hi from $(hostname)"' --modulepath . --nodes winrm://localhost -u Administrator -p redacted --no-ssl Prior behavior was the following debug output listing arguments passed to Ruby command run echo "hi from $(hostname)" --modulepath . --nodes winrm://localhost -u Administrator -p *redacated* --no-ssl output ruby.exe : Unknown argument(s) from, $(hostname) At line:4 char:5 + &$env:RUBY_DIR\bin\ruby -S -- $env:RUBY_DIR\bin\bolt $args + ~~ + CategoryInfo : NotSpecified: (Unknown argument(s) from, $(hostname):String ) [], RemoteException + FullyQualifiedErrorId : NativeCommandError
Jira (BOLT-1130) Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params
Title: Message Title Ethan Brown created an issue Puppet Task Runner / BOLT-1130 Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params Issue Type: Task Affects Versions: BOLT 1.11.0 Assignee: Unassigned Components: Windows Created: 2019/02/19 7:12 AM Labels: windows Priority: Normal Reporter: Ethan Brown BOLT-159 introduced a change to simplify argument passing from PowerShell when dealing with nested quotes. The change does improve the case mentioned, such that users can now use a simpler invocation like the following (rather than using """ themselves): bolt command run 'echo "hi from $(hostname)"' --modulepath . --nodes winrm://localhost -u Administrator -p Qu@lity! --no-ssl However, there are still cases where using more complex argument passing does not work properly due to not all values being escaped correctly for Ruby. In an ideal situation, a complex object should be serializable to a JSON string, which can then be passed directly
