Jira (PUP-8213) Error message for certificate name mismatch is clear as mud
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8213 Error message for certificate name mismatch is clear as mud Change By: Josh Cooper Fix Version/s: PUP 6.0.6 Fix Version/s: PUP 5.5.11 Fix Version/s: PUP 6.0.7 Fix Version/s: PUP 5.5.12 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 (PUP-9557) err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled
Title: Message Title Nihaz commented on PUP-9557 Re: err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled centraladmin07 is our Puppet master server and connections going 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-9557) err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled
Title: Message Title Nihaz commented on PUP-9557 Re: err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled [root@revproxynprd04 ~]# puppet agent --test --waitforcert 60 info: Creating a new SSL key for dmzproxynprd02.dmz.local err: Could not request certificate: execution expired err: Could not request certificate: execution expired err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled 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-9557) err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled
Title: Message Title Nihaz created an issue Puppet / PUP-9557 err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled Issue Type: Bug Assignee: Unassigned Created: 2019/03/12 5:54 PM Priority: Normal Reporter: Nihaz We have issues in RHEL 5 DMZ servers as Puppet clients are not regenerating certificates even though connected with Puppet Master. Updating all outputs below to trace out why the client is unable to request even though all are good [root@revproxynprd04 ~]# hostname revproxynprd04.dmz.local [root@revproxynprd04 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.11 (Tikanga) [root@revproxynprd04 ~]# telnet centraladmin07 8140 Trying 172.31.168.199... Connected to centraladmin07.news.newslimited.local (172.31.168.199). Escape character is '^]'. Connection closed by foreign host. [root@revproxynprd04 ~]# puppet agent -t --noop err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled [root@revproxynprd04 ~]# sudo puppet agent -t --debug --waitforcert=60 debug: Failed to load library 'rubygems' for feature 'rubygems' debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: /File[/var/lib/puppet/state/graphs]/seluser: Found seluser default 'system_u' for /var/lib/puppet/state/graphs debug: /File[/var/lib/puppet/state/graphs]/selrole: Found selrole default 'object_r' for /var/lib/puppet/state/graphs debug: /File[/var/lib/puppet/state/graphs]/seltype: Found seltype default 'var_lib_t' for /var/lib/puppet/state/graphs debug: /File[/var/lib/puppet/client_data]/seluser: Found seluser default 'system_u' for /var/lib/puppet/client_data debug: /File[/var/lib/puppet/client_data]/selrole: Found selrole default 'object_r' for /var/lib/puppet/client_data debug: /File[/var/lib/puppet/client_data]/seltype: Found seltype default 'var_lib_t' for /var/lib/puppet/client_data debug:
Jira (BOLT-1170) Unable to run apply() on Windows host - The current deserialized object size is xxx. The allowed maximum object size is 10485760
Title: Message Title Nick Maludy commented on BOLT-1170 Re: Unable to run apply() on Windows host - The current deserialized object size is xxx. The allowed maximum object size is 10485760 Doing some digging on this talking with Nick Lewis on Slack and found the following: All modules in modulepath have their files/ directory packaged up in a tarball: https://github.com/puppetlabs/bolt/blob/master/lib/bolt/applicator.rb#L27-L35 The tarball is then base64 encoded and added to that `apply` task's input: https://github.com/puppetlabs/bolt/blob/master/lib/bolt/applicator.rb#L182-L188 The task is then run via SSH / WinRM with the very large input parameters, causing the command overflow in PowerShell. I noticed that both the SSH and WinRM implementations support uploading auxiliary files along with a task: https://github.com/puppetlabs/bolt/blob/master/lib/bolt/transport/winrm.rb#L127-L130 https://github.com/puppetlabs/bolt/blob/master/lib/bolt/transport/ssh.rb#L154-L157 Potentially this could be used to upload the catalog and plugin tarball (most likely more efficient too). Then the task input should not grow over the command line limits and cause these type of failures. 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
Jira (PDB-4302) Build and test PuppetDB for el-8
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4302 Build and test PuppetDB for el-8 Issue Type: Task Assignee: Unassigned Created: 2019/03/12 5:10 PM Priority: Normal Reporter: Eric Griswold Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Release Notes Summary: Puppet will now treat owner and group on the file resource as in-sync in the following scenario:* owner / and group are not set in the resource* owner and / or group are set to the SYSTEM user on the running node. * the SYSTEM user ACE is set to Full ControlPuppet will allow users to specifically configure the SYSTEM user to less than FullControl by setting the owner and/or group parameters to 'SYSTEM' in the file resource. (i.e. if owner and/or group are set to 'SYSTEM' puppet will _not_ munge permissions to FullControl). In this case Puppet will emit a warning since setting SYSTEM to less than FullControl may have unintended consequences. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Release Notes Summary: Puppet will now treat owner and group on the file resource as in-sync in the following scenario:* owner/group are not set in the resource* owner/group are set to the SYSTEM user* the SYSTEM user ACE is set to Full ControlPuppet will allow users to specifically configure the SYSTEM user to less than FullControl by setting the owner and/or group parameters to 'SYSTEM' in the file resource. (i.e. if owner and/or group are set to 'SYSTEM' puppet will _not_ munge permissions to FullControl). In this case Puppet will emit a warning since setting SYSTEM to less than FullControl may have unintended consequences. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4232) Use of 'in' operator with ast_only: true causes NullPointerException
Title: Message Title Geoff Nichols commented on PDB-4232 Re: Use of 'in' operator with ast_only: true causes NullPointerException Great, thank you Austin Blatt! 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-4232) Use of 'in' operator with ast_only: true causes NullPointerException
Title: Message Title Austin Blatt commented on PDB-4232 Re: Use of 'in' operator with ast_only: true causes NullPointerException Geoff Nichols it's ready, I resolved it. 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-8213) Error message for certificate name mismatch is clear as mud
Title: Message Title Geoff Nichols commented on PUP-8213 Re: Error message for certificate name mismatch is clear as mud Josh Cooper, I'm following up on tickets targeted at the upcoming Platform 5.5.11 release. Is there anything left to do before this is resolved? 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-4257) PuppetDB skips message files with LONGNAME_HASH
Title: Message Title Geoff Nichols commented on PDB-4257 Re: PuppetDB skips message files with LONGNAME_HASH Rob Browning, I'm following up on tickets targeted at the upcoming Platform 5.5.11 release. Is there anything left to do before this is resolved? 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-4232) Use of 'in' operator with ast_only: true causes NullPointerException
Title: Message Title Geoff Nichols commented on PDB-4232 Re: Use of 'in' operator with ast_only: true causes NullPointerException Austin Blatt, I'm following up on tickets targeted at the upcoming Platform 5.5.11 release. Is there anything left to do before this is resolved? 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-4232) Use of 'in' operator with ast_only: true causes NullPointerException
Title: Message Title Geoff Nichols updated an issue PuppetDB / PDB-4232 Use of 'in' operator with ast_only: true causes NullPointerException Change By: Geoff Nichols Team: PuppetDB 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-4257) PuppetDB skips message files with LONGNAME_HASH
Title: Message Title Geoff Nichols updated an issue PuppetDB / PDB-4257 PuppetDB skips message files with LONGNAME_HASH Change By: Geoff Nichols Team: PuppetDB 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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Geoff Nichols commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run Sean McDonald, please provide 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-9496) Unable to use remote URI as source parameter with package provider on Windows
Title: Message Title Geoff Nichols commented on PUP-9496 Re: Unable to use remote URI as source parameter with package provider on Windows Branan Riley, please provide 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-9494) Update HA Documentation on enabling a replica
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-9494 Update HA Documentation on enabling a replica Change By: Geoff Nichols 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-3911) Resource events table should have a primary key
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3911 Resource events table should have a primary key Change By: Rob Browning Affects Version/s: PDB 6.3.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 (PDB-4257) PuppetDB skips message files with LONGNAME_HASH
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4257 PuppetDB skips message files with LONGNAME_HASH Previously PuppetDB was unable to process commands that were submitted with certnames containing characters like backslash, forward slash, colon, underscore, null, etc. or were "too long" (e.g. 200+ UTF-8 bytes), but only if PuppetDB was restarted after the commands were submitted and before they were processed. Now PuppetDB should handle those commands correctly. Change By: Rob Browning Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-4257) PuppetDB skips message files with LONGNAME_HASH
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4257 PuppetDB skips message files with LONGNAME_HASH Change By: Rob Browning Fix Version/s: PDB 6.3.0 Fix Version/s: PDB 6.0.3 Fix Version/s: PDB 5.2.8 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-4270) Support a new "configure expiration" command
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4270 Support a new "configure expiration" command Change By: Rob Browning Fix Version/s: PDB 6.0.3 Fix Version/s: PDB 5.2.8 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-4270) Support a new "configure expiration" command
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4270 Support a new "configure expiration" command Change By: Rob Browning Fix Version/s: PDB 6.3.0 Fix Version/s: PDB 6.0.3 Fix Version/s: PDB 5.2.8 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-4270) Support a new "configure expiration" command
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4270 Support a new "configure expiration" command Change By: Rob Browning Release Notes Summary: An experimental "configure expiration" command has been added. It currently allows specifying that factsets should (the longstanding default) or should not be candidates for expiration. See the documentation for further information and some caveats, and note that as an experimental command, it might be altered or removed in a future release. 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 (BOLT-1176) Tasks run on Windows via PCP do not resolve all executable paths correctly
Title: Message Title William Hurt created an issue Puppet Task Runner / BOLT-1176 Tasks run on Windows via PCP do not resolve all executable paths correctly Issue Type: Bug Assignee: Unassigned Components: bolt, Windows Created: 2019/03/12 12:16 PM Labels: windows powershell bolt tasks Priority: Normal Reporter: William Hurt When a PowerShell task is run on a Windows machine, there are differences in how it resolves paths to some executable files between runs via WinRM and PCP. When running a task that executes the following PowerShell snippet the results are as follows. Notice the path to puppet.bat resolves all the way down to the bat file: (Get-Command puppet) | Select-object * (Get-Command whoami) | Select-object * whoami The result via WinRM:
Jira (BOLT-1175) run_plan step
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1175 run_plan step Issue Type: New Feature Assignee: Unassigned Created: 2019/03/12 11:26 AM Priority: Normal Reporter: Alex Dreyer Allow a simple plan to call another plan as a step. That plan may be simple or puppet language. The parameters and variables set in the current plan should not be in the scope of the subplan. - plan: my_plan parameters: nodes: example.com param1: val
Jira (BOLT-1172) Support an eval step in simple plans.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1172 Support an eval step in simple plans. Change By: Alex Dreyer Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1174) run_script and file_upload steps
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1174 run_script and file_upload steps Issue Type: New Feature Assignee: Unassigned Created: 2019/03/12 11:23 AM Priority: Normal Reporter: Alex Dreyer Users should be able to run a script or upload a file as a step from a simple plan - script: foo target: example.com arguments: - arg1 - arg2 - source: mymodule/foo destination: /tmp/dest
Jira (BOLT-1171) Reference previous step results
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1171
Reference previous step results
Change By:
Alex Dreyer
After a named step is run it's result should be available in scope for the duration of the plan. It's results should not be inherited in the scope of subplans.All steps should have a {{name}} key that must be a valid puppet variable name.After a step is run the result should be available as {{$name}} in the current plan.All steps should also accept a {{description}} that can be used as a human readable description of the step.Having two steps with the same name or a shadowing an parameter should be an error.Step names cannot use variablesDescriptions should be allowed to use variables.{noformat} --- Make example here. steps: - name: one task: echoparameters: message: "hey there" - task: echo parameters: message: $one[0][_output] {noformat} Note this ticket will either be dependent on indexing into the result variable or having an eval step that can return simple values since a {{ResultSet}} is not a valid task parameter.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3911) Resource events table should have a primary key
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-3911 Resource events table should have a primary key Change By: Robert Roland Release Notes Summary: This adds a primary key to the resource_events table, which allows the use of pg_repack to reclaim space without taking the table offline, like the current "vacuum full" approach does.This will rewrite the entire resource_events table, so you will need to have more than the existing table's size available during the upgrade. The upgrade time is relative to the size of your table. 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
Jira (BOLT-1173) Make some step keys variable aware
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1173 Make some step keys variable aware Change By: Alex Dreyer Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1173) Make some step keys variable aware
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1173
Make some step keys variable aware
Change By:
Alex Dreyer
Questions to answer:Do we want strings to behave as they do in puppet should how it's quoted matter?Do we want to only handle strings that start with $?How do we handle variables in arrays?How do we minimize escaping?What keys should not be variable aware other than name?Experiment 1:can we look at the "style" of the yaml from the parser and handle different types of strings separately?don't interpolate inside {{'}}interpolate inside {{"}} "$var" should be the string var.evaluate unquotedliteral multiline should behave like {{"}}folded should be folded and not interpolatedevaluate each array element separately.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-9556) Add puppet ssl bootstrap action
Title: Message Title Josh Cooper created an issue Puppet / PUP-9556 Add puppet ssl bootstrap action Issue Type: Improvement Assignee: Unassigned Created: 2019/03/12 9:49 AM Fix Versions: PUP 6.4.0 Priority: Normal Reporter: Josh Cooper Add a bootstrap action to the puppet ssl application for running the state machine for downloading a CA, CRL and private key, client cert. This way users don't have to apply a catalog to get a client cert. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-9556) Add puppet ssl bootstrap action
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9556 Add puppet ssl bootstrap action Change By: Josh Cooper 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-9556) Add puppet ssl bootstrap action
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9556 Add puppet ssl bootstrap action Change By: Josh Cooper Sprint: Coremunity 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-9459) Create SSL state machine for generating a client cert
Title: Message Title Josh Cooper commented on PUP-9459 Re: Create SSL state machine for generating a client cert Acceptance criteria Private key should have permissions based on Puppet[:hostprivkey]. When running on a puppetserver host, the private key and client cert must be owned by the puppet user so it is readable by puppetserver. The state machine should download a missing CA If Puppet[:certificate_revocation] = :leaf or :chain, then the state machine should download a missing CRL. If Puppet[:certificate_revocation] = false, then the agent should not download or load a CRL. It should successfully connect to the server, even if the server's cert has been revoked. Calling Puppet::SSL::Host.localhost should run the client state machine, as there is existing code relying on that behavior: https://github.com/puppetlabs/puppet-agent-bootstrap/blob/master/lib/puppet/face/bootstrap.rb#L50 The generated CSR should contain custom_attributes and extension_requests if specified in Puppet[:csr_attributes]. The former are only added to the CSR. The latter are added to the CSR and copied to the signed client cert. The client state machine should work when autosigning is enabled If autosigning is disabled, and the agent should wait for Puppet[:waitforcert] seconds and try again. When the CSR is next signed, the agent should download the cert and finish its run. If Puppet[:waitforcert] = 0 or Puppet[:onetime] = true (which occurs when running puppet agent -t), then puppet should exit with an error message Exiting; no certificate found and waitforcert is disabled and exit code 1, like it does today. If an agent submits a CSR, but doesn't have a client cert, and you run puppetserver ca clean --certname , then the next time the agent runs (or wakes up), it should successfully submit the CSR again. If an agent has a client cert, but you clean the agent (puppet ssl clean), and run puppet agent -t, then puppet should submit a new CSR, but result in an error that the server's CSR doesn't match the client's. It should be possible to run puppetserver ca clean --certname on the server, and when the agent next checks it, it should successfully submit the CSR. You shouldn't have to delete any files from the agent.
Jira (BOLT-1173) Make some step keys variable aware
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1173 Make some step keys variable aware Issue Type: New Feature Assignee: Unassigned Created: 2019/03/12 9:43 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 this group at
Jira (FACT-1913) Build Facter for JRuby on RHEL8
Title: Message Title Maggie Dreyer created an issue Facter / FACT-1913 Build Facter for JRuby on RHEL8 Issue Type: Task Assignee: Unassigned Created: 2019/03/12 9:38 AM Priority: Normal Reporter: Maggie Dreyer The Facter configs in puppet-agent need to be updated to build Facter for JRuby on the new platform. This https://github.com/puppetlabs/puppet-agent/blob/master/configs/components/facter.rb#L43-L44 needs to be updated to include el-8. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1172) Support an eval step in simple plans.
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-1172
Support an eval step in simple plans.
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2019/03/12 9:32 AM
Priority:
Normal
Reporter:
Alex Dreyer
This step should evaluate a string of puppet code and return the result. Variable assignments in the string should not be available in the plans scope. The plans scope should be available when evaluating the string. run_* commands should be documented as not a best practice in eval blocks but not prevented. How does the eval string get quoted?
name: myeval
eval: get_targets($nodes).map |$n| { $n.name }
Add
Jira (BOLT-1119) SPIKE - understand why bolt is so slow on windows
Title: Message Title Ethan Brown commented on BOLT-1119 Re: SPIKE - understand why bolt is so slow on windows Using a Windows 10 local VM with Ruby 2.5 and running Ruby / Bolt from source (with bundler) inside the ruby-prof profiler has generated some useful information. A typical bundle exec bolt --help on a clean system takes about 4.5 seconds. By comparison, simply loading irb takes under a second. There are two areas to further explore: About 85% of the time is spent in Rubys Kernel.require. While it's unlikely that performance of that core Ruby call can be improved, we may be able to make some optimizations around when code is loaded. In areas where code can be lazy loaded, it may be advantageous to do so, since expectations are that a typical --help should respond immediately. Next step is to add something like https://github.com/ruby-prof/ruby-prof/issues/159 to introduce more diagnostic information / analyze further. It's not yet determined if the majority of this time is loading PAL (Puppet As Library) - which it very well may be. 18% of the time is spent in a gem scan performed by the LittlePlugger gem - specifically in this line - https://github.com/TwP/little-plugger/blob/master/lib/little-plugger.rb#L191 (It's possible that loggers plugin system may be disabled to avoid running this code path) A couple of additional notes: Focus thus far has been on the most simple of cases - improving the experience around loading Bolt help. Additional work is still TBD for loading actual module / plan code and metadata, running tasks, etc. At least in this test environment, installing more gem code to the Ruby module path appears to degrade performance. Run times of 4.5 seconds lengthen to 5+ seconds. Other local changes have caused runs to degrade to 12+ seconds (still investigating if this is an anomaly or reproducible) Add Comment
Jira (BOLT-1171) Reference previous step results
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1171 Reference previous step results Issue Type: New Feature Assignee: Unassigned Created: 2019/03/12 9:26 AM Priority: Normal Reporter: Alex Dreyer After a named step is run it's result should be available in scope for the duration of the plan. It's results should not be inherited in the scope of subplans. All steps should have a name key that must be a valid puppet variable name. After a step is run the result should be available as $name in the current plan. All steps should also accept a description that can be used as a human readable description of the step. Having two steps with the same name or a shadowing an parameter should be an error. Step names cannot use variables Descriptions should be allowed to use variables. Make example here.
Jira (BOLT-1153) Support parameters for simple plans
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1153 Support parameters for simple plans Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1132) Environment variables do not propagate to actions run on localhost.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1132 Environment variables do not propagate to actions run on localhost. 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 (FACT-1911) Cannot find libfacter when starting Server on RHEL 8
Title: Message Title Maggie Dreyer commented on FACT-1911 Re: Cannot find libfacter when starting Server on RHEL 8 I'm testing that change now with puppetserver. 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-1911) Cannot find libfacter when starting Server on RHEL 8
Title: Message Title Mihai Buzgau commented on FACT-1911 Re: Cannot find libfacter when starting Server on RHEL 8 fixed in https://github.com/puppetlabs/puppet-agent/pull/1667 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-1911) Cannot find libfacter when starting Server on RHEL 8
Title: Message Title Denis Susan assigned an issue to Denis Susan Facter / FACT-1911 Cannot find libfacter when starting Server on RHEL 8 Change By: Denis Susan Assignee: Denis Susan 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-1911) Cannot find libfacter when starting Server on RHEL 8
Title: Message Title
Justin Stoller updated an issue
Facter / FACT-1911
Cannot find libfacter when starting Server on RHEL 8
Change By:
Justin Stoller
when attempting to start puppetserver (by {{systemctl start puppetserver}}) it fails to start, here are the relevant logs:{code:java}2019-03-11T16:52:53.427Z ERROR [async-dispatch-2] [p.t.internal] Error during service init!!!java.lang.IllegalStateException: Unable to borrow JRubyInstance from poolat puppetlabs.services.jruby_pool_manager.impl.jruby_internal$fn__32380$borrow_from_pool_BANG__STAR___32385$fn__32386.invoke(jruby_internal.clj:268)at java.lang.Thread.run(Thread.java:748)Caused by: org.jruby.embed.EvalFailedException: (LoadError) libfacter was not built with JRuby support.at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:131)at RUBY.(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:59)2019-03-11T16:52:53.431Z INFO [main] [p.t.internal] Beginning shutdown sequence2019-03-11T16:52:53.426Z ERROR [clojure-agent-send-pool-0] [p.t.internal] shutdown-on-error triggered because of exception!java.lang.IllegalStateException: There was a problem adding a JRubyInstance to the pool.at puppetlabs.services.jruby_pool_manager.impl.jruby_agents$fn__32598$prime_pool_BANG___32603$fn__32607.invoke(jruby_agents.clj:75){code}To reproduce: # check out the {{git://github.com/puppetlabs/puppetserver}} repo # recursively update the submodules within # edit {{acceptance/scripts/generic/testrun.sh}} like ** {code}-export GENCONFIG_LAYOUT="${GENCONFIG_LAYOUT:-redhat6-64ma-ubuntu1604-64a-windows2012r2-64a}"+export GENCONFIG_LAYOUT="${GENCONFIG_LAYOUT:-redhat8-64ma-ubuntu1604-64a}"{code} # {{export PACKAGE_BUILD_VERSION=6.2.2.SNAPSHOT.2019.03.09T1350}} # run {{./acceptance/scripts/generic/testrun.sh -p }}Should fail on {{acceptance/suites/pre_suites/foss/71_smoke_test_puppetserver.rb}}.
Add Comment
Jira (FACT-1911) Cannot find libfacter when starting Server on RHEL 8
Title: Message Title Maggie Dreyer commented on FACT-1911 Re: Cannot find libfacter when starting Server on RHEL 8 Puppet Server cannot be tested on RHEL 8 on any branch until this is fixed, since it prevents the server from starting on that platform. 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-1911) Cannot find libfacter when starting Server on RHEL 8
Title: Message Title
Justin Stoller updated an issue
Facter / FACT-1911
Cannot find libfacter when starting Server on RHEL 8
Change By:
Justin Stoller
when attempting to start puppetserver (by {{systemctl start }} puppetserver}}) it fails to start, here are the relevant logs:{code:java}2019-03-11T16:52:53.427Z ERROR [async-dispatch-2] [p.t.internal] Error during service init!!!java.lang.IllegalStateException: Unable to borrow JRubyInstance from poolat puppetlabs.services.jruby_pool_manager.impl.jruby_internal$fn__32380$borrow_from_pool_BANG__STAR___32385$fn__32386.invoke(jruby_internal.clj:268)at java.lang.Thread.run(Thread.java:748)Caused by: org.jruby.embed.EvalFailedException: (LoadError) libfacter was not built with JRuby support.at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:131)at RUBY.(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:59)2019-03-11T16:52:53.431Z INFO [main] [p.t.internal] Beginning shutdown sequence2019-03-11T16:52:53.426Z ERROR [clojure-agent-send-pool-0] [p.t.internal] shutdown-on-error triggered because of exception!java.lang.IllegalStateException: There was a problem adding a JRubyInstance to the pool.at puppetlabs.services.jruby_pool_manager.impl.jruby_agents$fn__32598$prime_pool_BANG___32603$fn__32607.invoke(jruby_agents.clj:75){code}To reproduce: # check out the {{git://github.com/puppetlabs/puppetserver}} repo # recursively update the submodules within # edit {{acceptance/scripts/generic/testrun.sh}} like ** {code}-export GENCONFIG_LAYOUT="${GENCONFIG_LAYOUT:-redhat6-64ma-ubuntu1604-64a-windows2012r2-64a}"+export GENCONFIG_LAYOUT="${GENCONFIG_LAYOUT:-redhat8-64ma-ubuntu1604-64a}"{code} # {{export PACKAGE_BUILD_VERSION=6.2.2.SNAPSHOT.2019.03.09T1350}} # run {{./acceptance/scripts/generic/testrun.sh}}Should fail on {{acceptance/suites/pre_suites/foss/71_smoke_test_puppetserver.rb}}.
Add Comment
Jira (FACT-1911) Cannot find libfacter when starting Server on RHEL 8
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1911 Cannot find libfacter when starting Server on RHEL 8 Change By: Maggie Dreyer Priority: Normal Blocker 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-994) Task helper code for leveraging puppet device
Title: Message Title David Armstrong commented on BOLT-994 Re: Task helper code for leveraging puppet device Currently part of https://github.com/puppetlabs/puppetlabs-panos/pull/73 with a view to move to the Resource API. 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-994) Task helper code for leveraging puppet device
Title: Message Title David Armstrong assigned an issue to David Armstrong Puppet Task Runner / BOLT-994 Task helper code for leveraging puppet device Change By: David Armstrong Assignee: David Armstrong 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-2354) agent is confused about cert state
Title: Message Title Mohak Sharma commented on PUP-2354 Re: agent is confused about cert state Hi Josh, I have set autosign to a bash script which return zero or non-zero status according to some logic and enables autosigning from a legitimate source. Just want to make sure according to the limitations listed by you, will it work if I set allow_duplicate_certs to true? 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-9554) split should allow splitting by raw string
Title: Message Title Henrik Lindberg commented on PUP-9554 Re: split should allow splitting by raw string The proposed change would be backwards incompatible and would therefore have to be done on a major version boundary. The change would also be problematic to handle since the change means split would behave differently and would need a period of "deprecation" (a message being logged for each call to split where the pattern is not a regexp). Given the amount of work involved I am not sure it is worth changing. I think adding a regexp escape function to puppet would work though. 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-1912) Should be possible to merge structured facts
Title: Message Title Matthias Baur commented on FACT-1912 Re: Should be possible to merge structured facts This feature would allow a better name spacing of facts. Lets take the "apt" facts as an example: root@test:/# facter -p | grep ^apt apt_dist_updates => 3 apt_has_dist_updates => true apt_has_updates => true apt_package_dist_updates => [ apt_package_security_dist_updates => [ apt_package_security_updates => [ apt_package_updates => [ apt_reboot_required => false apt_security_dist_updates => 3 apt_security_updates => 3 apt_update_last_success => 1552361391 apt_updates => 3
Jira (FACT-1912) Should be possible to merge structured facts
Title: Message Title Matthias Baur created an issue Facter / FACT-1912 Should be possible to merge structured facts Issue Type: New Feature Assignee: Unassigned Created: 2019/03/12 1:27 AM Priority: Normal Reporter: Matthias Baur (Copied from https://projects.puppetlabs.com/issues/20408 originally created by Erik Dalén) To be able to extend one structured fact with more data it should be possible to deep merge two facts. For example it there was a “interfaces” hash containing network interfaces and info about them and you wanted to add LLDP information to them you could add another interfaces fact that would get deep merged with the original one. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-3745) Group membership should be a type of its own.
Title: Message Title Victor Engmark commented on PUP-3745 Re: Group membership should be a type of its own. `groupadd` at least on Arch Linux (from shadow-utils 4.6) supports `-r`/`–system`. Is this all that's needed to change the support matrix? 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.
