Jira (BOLT-583) Unable to use "localhost" as a node on Windows
Title: Message Title Glenn Sarti created an issue Puppet Task Runner / BOLT-583 Unable to use "localhost" as a node on Windows Issue Type: Bug Affects Versions: BOLT 0.20.5 Assignee: Unassigned Created: 2018/06/12 8:25 PM Priority: Normal Reporter: Glenn Sarti When running a PowerShell task on a local computer with a correctly configured WinRM service, but with the target node of 'localhost' I get a message saying it's not supported and really obtuse error stack. Using a simple trick of --nodes '127.0.0.1' works around the issue. Note - The IP6 loopback ::1 does not work example C:\Source\puppetlabs-wsus_client [(f2ade67...) +1 ~0 -0 !]> bolt task run wsus_client::update_history --modulepath .\spec\fixtures\modules\ --nodes localhost --transport winrm --no-ssl --user --password Please enter your password: C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/transport/local.rb:24:in `initialize': The local transport is not yet implemented on Windows (NotImplementedError)
Jira (PUP-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Glenn Sarti commented on PUP-6729 Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators I've created PUP-8939 to capture the "Local Admin cannot run Puppet after installed by SYSTEM" 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-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title Glenn Sarti commented on PUP-8939 Re: Administrators are not able to run puppet agent when installed as SYSTEM in some cases Cloned PUP-6729 and removed the information that doesn't relate to the SYSTEM to Local Admin 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.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8939 Administrators are not able to run puppet agent when installed as SYSTEM in some cases Change By: Glenn Sarti Comment: A comment with security level 'Developers' was removed. 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-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8939 Administrators are not able to run puppet agent when installed as SYSTEM in some cases Change By: Glenn Sarti Comment: Yeah, the symptoms are the same, but I think the cause is different. Let's spin off a new ticket for this new repro, which has deviated quite a bit from the original description. 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-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-8939
Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Change By:
Glenn Sarti
Comment:
From a different system, which is much fresher, but showing the same issue. In this case, it's trying to copy into clientbucket/9/e/:{noformat}PS C:\ProgramData\PuppetLabs\puppet\cache> Get-Acl . | select *Get-Acl . | select *PSPath : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\PuppetLabs\puppet\cachePSParentPath: Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\PuppetLabs\puppetPSChildName : cachePSDrive : CPSProvider : Microsoft.PowerShell.Core\FileSystemCentralAccessPolicyId :CentralAccessPolicyName :Path: Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\PuppetLabs\puppet\cacheOwner : QMZMML8VXJ0JTSW\AdministratorGroup : QMZMML8VXJ0JTSW\NoneAccess : {System.Security.AccessControl.FileSystemAccessRule, System.Security.AccessControl.FileSystemAccessRule, System.Security.AccessControl.FileSystemAccessRule, System.Security.AccessControl.FileSystemAccessRule...}Sddl: O:LAG:S-1-5-21-1327426001-2876377404-380743070-513D:AI(A;OICIID;FA;;;SY)(A;OICIID;FA;;;BA)(A; ID;FA;;;LA)(A;OICIIOID;GA;;;CO)(A;OICIID;0x1200a9;;;BU)(A;CIID;DCLCRPCR;;;BU)AccessToString : NT AUTHORITY\SYSTEM Allow FullControl BUILTIN\Administrators Allow FullControl QMZMML8VXJ0JTSW\Administrator Allow FullControl CREATOR OWNER Allow 268435456 BUILTIN\Users Allow ReadAndExecute, Synchronize BUILTIN\Users Allow WriteAuditToString :AccessRightType : System.Security.AccessControl.FileSystemRightsAccessRuleType : System.Security.AccessControl.FileSystemAccessRuleAuditRuleType : System.Security.AccessControl.FileSystemAuditRuleAreAccessRulesProtected : FalseAreAuditRulesProtected : FalseAreAccessRulesCanonical : True{noformat}{noformat}PS C:\ProgramData\PuppetLabs\puppet\cache\clientbucket> Get-Acl . | select *Get-Acl . | select *PSPath : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\PuppetLabs\puppet\cache\clientbucketPSParentPath: Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\PuppetLabs\puppet\cachePSChildName : clientbucketPSDrive : CPSProvider : Microsoft.PowerShell.Core\FileSystemCentralAccessPolicyId :CentralAccessPolicyName :Path: Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\PuppetLabs\puppet\cache\clientbucketOwner : BUILTIN\AdministratorsGroup : NT AUTHORITY\SYSTEMAccess : {System.Security.AccessControl.FileSystemAccessRule, System.Security.AccessControl.FileSystemAccessRule, System.Security.AccessControl.FileSystemAccessRule, System.Security.AccessControl.FileSystemAccessRule...}Sddl:
Jira (PUP-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-8939
Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Change By:
Glenn Sarti
Comment:
As (I think) a consequence of this issue, if you sometimes run puppet from the service (or from the orchestrator) but sometimes run 'puppet agent -t' as Administrator, the permissions can get mixed up. The case I encountered a few times was corruption of the permissions on puppet/cache/clientbucket: (named .bak here){noformat}C:\ProgramData\PuppetLabs\puppet\cache\clientbucket.bak>ls -lls -ltotal 0drwxr-x---+ 1 Administrators SYSTEM 0 Dec 1 21:38 1drwxr-x---+ 1 Administrator None 0 Dec 1 20:43 3drwxr-x---+ 1 Administrator None 0 Dec 1 20:58 4drwxr-x---+ 1 Administrators SYSTEM 0 Dec 1 21:31 5drwxr-x---+ 1 Administrator None 0 Dec 1 21:09 6drwxr-x---+ 1 Administrator None 0 Dec 1 17:25 7drwxr-x---+ 1 Administrator None 0 Dec 1 21:11 8drwxr-x---+ 1 Administrator None 0 Dec 1 21:02 9drwxr-x---+ 1 Administrator None 0 Dec 1 20:54 adrwxr-x---+ 1 Administrators SYSTEM 0 Dec 1 21:39 bdrwxr-x---+ 1 Administrators SYSTEM 0 Dec 1 18:27 c{noformat}I believe the sequence to get to this state was me first running 'puppet agent -t' at the console as Administrator, then later running puppet with the orchestrator. The latter failed, while trying to copy a file into the '4' subdirectory. This resulted in getting 'permission denied' errors when trying to copy a config file into clientbucket before changing it. This is a very common workflow, and if it can so easily bork the agent installation, we should fix it.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title Glenn Sarti created an issue Puppet / PUP-8939 Administrators are not able to run puppet agent when installed as SYSTEM in some cases Issue Type: Improvement Affects Versions: PUP 5.5.1 Assignee: Glenn Sarti Created: 2018/06/12 6:37 PM Fix Versions: PUP 6.0.0 Priority: Major Reporter: Glenn Sarti This issue was created from the work in PUP-6729 — In some instances when Puppet Agent is installed as SYSTEM, the local administrators are unable to run puppet agent interactively. Add Comment
Jira (PUP-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8939 Administrators are not able to run puppet agent when installed as SYSTEM in some cases Change By: Glenn Sarti Comment: A comment with security level 'Developers' was removed. 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-560) (DOCS) Explore importing JSON documentation to DITA
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-560 (DOCS) Explore importing JSON documentation to DITA Change By: Kate Lopresti Attachment: boltlib.html 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-560) (DOCS) Explore importing JSON documentation to DITA
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-560 (DOCS) Explore importing JSON documentation to DITA Change By: Kate Lopresti Attachment: boltlib.xml 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-560) (DOCS) Explore importing JSON documentation to DITA
Title: Message Title Kate Lopresti commented on BOLT-560 Re: (DOCS) Explore importing JSON documentation to DITA First step: locally converted JSON to XML. Attached the file generated in Oxygen XML editor. boltlib.xml 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-560) (DOCS) Explore importing JSON documentation to DITA
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-560 (DOCS) Explore importing JSON documentation to DITA Change By: Kate Lopresti Attachment: boltlib.html 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-8748) Puppet::Rest::Client should allow its verify mode to be configured by the caller
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8748 Puppet::Rest::Client should allow its verify mode to be configured by the caller Change By: Maggie Dreyer Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8938) zypper package provider fails to downgrade packages
Title: Message Title Stuart Lamble created an issue Puppet / PUP-8938 zypper package provider fails to downgrade packages Issue Type: Bug Affects Versions: PUP 5.5.2 Assignee: Unassigned Components: Types and Providers Created: 2018/06/12 4:12 PM Environment: Puppet agent 5.5.2 SLES 12 SP2 Priority: Minor Reporter: Stuart Lamble When specifying a specific version of a package (ensure => ...), the zypper provider tries to install that package using the command: /usr/bin/zypper --quiet install --auto-agree-with-licenses --no-confirm- This fails - running the command without the --quiet switch reveals the error: The selected package '-' from repository
Jira (PUP-8828) Package module into puppet-agent
Title: Message Title Melissa Stone commented on PUP-8828 Re: Package module into puppet-agent Merged into puppet-agent master at https://github.com/puppetlabs/puppet-agent/commit/5b39b72036c2303d6f2237e731a5ea8cdb6b587f 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-566) Create syntax examples for applying manifest code from a plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-566
Create syntax examples for applying manifest code from a plan
Change By:
Alex Dreyer
What options are possible for applying a manifest from puppet code without relying on heredocs or external files. The result of this ticket should be a few options that are feasible in the parse and can be user tested.Requirements1. Accepts arguments2. Accepts a chunk of inline manifest code3. Probably starts with a recognizable understandable keyword4. Should not allow nested invocationsQuestions:1. What examples do we want to use for the user test(https://github.com/puppetlabs/plan_resources/blob/master/progression/plans/two.pp)2. What non-lambda syntax do we want? we're cutting this until we hear otherwise from users.3. How should apply work? it should take a path to a .pp file in the modules files directory. apply('module/files/my_manifest.pp', $targets, $options) The example should include a call to a function that loads local json. something like load_json('~/src/my_app/schema.json')
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1862) add support for openSUSE LEAP 15
Title: Message Title Scott McClellan updated an issue Facter / FACT-1862 add support for openSUSE LEAP 15 Change By: Scott McClellan Labels: opensuse 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-1862) add support for openSUSE LEAP 15
Title: Message Title Scott McClellan assigned an issue to Branan Riley Facter / FACT-1862 add support for openSUSE LEAP 15 Change By: Scott McClellan Assignee: Branan Riley 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-8937) AIX package installation is not checking state of the package
Title: Message Title Scott McClellan updated an issue Puppet / PUP-8937 AIX package installation is not checking state of the package Change By: Scott McClellan Labels: aix customer package type_and_provider Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8937) AIX package installation is not checking state of the package
Title: Message Title Scott McClellan updated an issue Puppet / PUP-8937 AIX package installation is not checking state of the package Change By: Scott McClellan Issue Type: Improvement Bug 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-8937) AIX package installation is not checking state of the package
Title: Message Title Scott McClellan updated an issue Puppet / PUP-8937 AIX package installation is not checking state of the package Change By: Scott McClellan Labels: aix package type_and_provider Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8937) AIX package installation is not checking state of the package
Title: Message Title Scott McClellan updated an issue Puppet / PUP-8937 AIX package installation is not checking state of the package Change By: Scott McClellan Team: 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-8937) AIX package installation is not checking state of the package
Title: Message Title Scott McClellan moved an issue Puppet / PUP-8937 AIX package installation is not checking state of the package Change By: Scott McClellan Key: PA PUP - 2071 8937 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Branan Riley updated an issue Facter / FACT-1858 Provide an option to disable legacy facts so they are not sent to the master from the agent Change By: Branan Riley Team: 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 (FACT-1859) Facter tries to load localizations from non-existent paths
Title: Message Title Scott McClellan updated an issue Facter / FACT-1859 Facter tries to load localizations from non-existent paths Change By: Scott McClellan Security: Internal 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-1859) Facter tries to load localizations from non-existent paths
Title: Message Title Scott McClellan assigned an issue to Branan Riley Facter / FACT-1859 Facter tries to load localizations from non-existent paths Change By: Scott McClellan Assignee: Branan Riley 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-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Scott McClellan commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent Branan Riley to update with scope. 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-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Scott McClellan assigned an issue to Branan Riley Facter / FACT-1858 Provide an option to disable legacy facts so they are not sent to the master from the agent Change By: Scott McClellan Assignee: Branan Riley 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-3938) Update master to appropriate clj-parent branch
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3938 Update master to appropriate clj-parent branch Issue Type: Improvement Assignee: Unassigned Created: 2018/06/12 1:51 PM Priority: Normal Reporter: Rob Browning Looks like that'd currently be master, i.e. 2.0.x. Also see if we can/should add travis testing against the tip if it's easy, or create another ticket if it needs investigation, or more effort. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8926) Prepare release announcement (Puppet Platform 5.3.8)
Title: Message Title Garrett Guillotte commented on PUP-8926 Re: Prepare release announcement (Puppet Platform 5.3.8) See https://tickets.puppetlabs.com/browse/DOC-3636?focusedCommentId=566704=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-566704 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-8933) Prepare release announcement (Puppet Platform 5.5.3)
Title: Message Title Garrett Guillotte commented on PUP-8933 Re: Prepare release announcement (Puppet Platform 5.5.3) See https://tickets.puppetlabs.com/browse/DOC-3636?focusedCommentId=566704=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-566704 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-3652) Throw cli-errors trapperkeeper will actually recognize
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3652 Throw cli-errors trapperkeeper will actually recognize Change By: Zachary Kent Assignee: Zachary Kent 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-3936) Add pipeline in ci-job-config for PDBext master branch
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3936 Add pipeline in ci-job-config for PDBext master branch Change By: Zachary Kent Assignee: Zachary Kent 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-3905) Update jenkins pipelines so that final builds have SHIP_NIGHTLY=false
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3905 Update jenkins pipelines so that final builds have SHIP_NIGHTLY=false Change By: Zachary Kent Assignee: Zachary Kent 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-3936) Add pipeline in ci-job-config for PDBext master branch
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3936 Add pipeline in ci-job-config for PDBext master branch Change By: Zachary Kent Assignee: Zachary Kent 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-582) Puppet specifications PR for plan language
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-582 Puppet specifications PR for plan language Issue Type: Task Assignee: Unassigned Created: 2018/06/12 10:53 AM Priority: Normal Reporter: Alex Dreyer We should add a PR to puppet specifications to cover the plan language. We should start to codify the plan language in puppet-specifications plan construct apply keyword plan functions plan datatypes Add Comment
Jira (PUP-8797) Extract the code & verify the module
Title: Message Title Melissa Stone commented on PUP-8797 Re: Extract the code & verify the module Merged in with https://github.com/puppetlabs/puppetlabs-selinux_core/commit/f97be453dcd5935551e507d1e10bb91b3ae6c72a 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-8936) Communicate scope and timeline of next release (Puppet Platform 5.5.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8936 Communicate scope and timeline of next release (Puppet Platform 5.5.3) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:25 AM Due Date: 2018/06/14 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-8935) Update Confluence and JIRA based on release (Puppet Platform 5.5.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8935 Update Confluence and JIRA based on release (Puppet Platform 5.5.3) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:25 AM Due Date: 2018/06/14 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description
Jira (PUP-8932) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8932 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.3) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:24 AM Due Date: 2018/06/07 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-8933) Prepare release announcement (Puppet Platform 5.5.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8933 Prepare release announcement (Puppet Platform 5.5.3) Issue Type: Task Assignee: Garrett Guillotte Created: 2018/06/12 10:24 AM Due Date: 2018/06/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) Please paste the text of the announcement in the 'Send announcement' ticket. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-8934) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8934 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.3) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:24 AM Due Date: 2018/06/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-8926) Prepare release announcement (Puppet Platform 5.3.8)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8926 Prepare release announcement (Puppet Platform 5.3.8) Issue Type: Task Assignee: Garrett Guillotte Created: 2018/06/12 10:12 AM Due Date: 2018/06/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) Please paste the text of the announcement in the 'Send announcement' ticket. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-8930) Puppet Platform 5.5.3 Release - 2018-06-13
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8930 Puppet Platform 5.5.3 Release - 2018-06-13 Issue Type: Epic Assignee: Kenn Hussey Created: 2018/06/12 10:23 AM Due Date: 2018/06/13 Priority: Normal Reporter: Kenn Hussey Puppet Platform 5.5.3 Release - 2018-06-13 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8931) Prepare JIRA for release (Puppet Platform 5.5.3)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8931 Prepare JIRA for release (Puppet Platform 5.5.3) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:23 AM Due Date: 2018/06/07 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 4) Update the “master” filters for Puppet Platform 5.5.3 and puppet-agent 5.5.3 to reference the “Fixed in” filters created above. 5) Update the community feedback filter for Puppet Platform X.y to reference the “Introduced in” filter created above.
Jira (PDB-3937) Ensure the puppetdb-postgresql docker container has a reasonable config
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3937 Ensure the puppetdb-postgresql docker container has a reasonable config Issue Type: Improvement Assignee: Unassigned Created: 2018/06/12 10:22 AM Priority: Normal Reporter: Rob Browning Postgresql has notoriously conservative defaults. If that's also true for the container, then we may want to adjust them. Check and see. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8928) Update Confluence and JIRA based on release (Puppet Platform 5.3.8)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8928 Update Confluence and JIRA based on release (Puppet Platform 5.3.8) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:13 AM Due Date: 2018/06/14 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description
Jira (PUP-8923) Puppet Platform 5.3.8 Release - 2018-06-13
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8923 Puppet Platform 5.3.8 Release - 2018-06-13 Issue Type: Epic Assignee: Kenn Hussey Created: 2018/06/12 10:12 AM Due Date: 2018/06/13 Priority: Normal Reporter: Kenn Hussey Puppet Platform 5.3.8 Release - 2018-06-13 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8929) Communicate scope and timeline of next release (Puppet Platform 5.3.8)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8929 Communicate scope and timeline of next release (Puppet Platform 5.3.8) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:13 AM Due Date: 2018/06/14 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-8927) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.3.8)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8927 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.3.8) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:12 AM Due Date: 2018/06/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-8924) Prepare JIRA for release (Puppet Platform 5.3.8)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8924 Prepare JIRA for release (Puppet Platform 5.3.8) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:12 AM Due Date: 2018/06/07 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 4) Update the “master” filters for Puppet Platform 5.3.8 and puppet-agent 5.3.8 to reference the “Fixed in” filters created above. 5) Update the community feedback filter for Puppet Platform X.y to reference the “Introduced in” filter created above.
Jira (PUP-8925) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.3.8)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8925 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.3.8) Issue Type: Task Assignee: Kenn Hussey Created: 2018/06/12 10:12 AM Due Date: 2018/06/07 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-06-13) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (BOLT-579) I want to know what output format bolt is using
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-579 I want to know what output format bolt is using 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-564) I want to know how often each plan function is run
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-564 I want to know how often each plan function is run 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-556) Submit puppet-specifications PR for multi-file tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-556 Submit puppet-specifications PR for multi-file tasks 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 (BOLT-580) design/spike on bolt-transport api
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-580 design/spike on bolt-transport api 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-580) design/spike on bolt-transport api
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-580 design/spike on bolt-transport api Change By: Alex Dreyer Come up with a proposal for a new runtime based on bolt transports that could be used by orchestrator. A spike in bolt be may be helpful but is not required.1. What is the API between it and orchestrator2. How much work will it be implementRequirements:- Should not read config file from disk- Should support multi-threading- Should accept streaming stdin of single targets to run on- It should stream events/results as ready on stdout.- keep in mind that discovery may want to use this as well.- Should not run as it's own service in the initial estimate - Orchestrator should pass a task object as input in this iteration(JSON metadata + file data) 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 (BOLT-566) Create syntax examples for applying manifest code from a plan
Title: Message Title Henrik Lindberg commented on BOLT-566 Re: Create syntax examples for applying manifest code from a plan Thanks Alex Dreyer, that is an efficient way to clear the cached state Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-580) design/spike on bolt-transport api
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-580 design/spike on bolt-transport api Change By: Alex Dreyer Come up with a proposal for a new runtime based on bolt transports that could be used by orchestrator. A spike in bolt be may be helpful but is not required.1. What is the API between it and orchestrator2. How much work will it be implementRequirements:- Should not read config file from disk- Should support multi-threading- Should accept streaming stdin of single targets to run on- It should stream events/results as ready on stdout.- keep in mind that discovery may want to use this as well.- Should not run as it's own service . in the initial estimate 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,
Jira (BOLT-580) design/spike on bolt-transport api
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-580 design/spike on bolt-transport api Change By: Alex Dreyer Come up with a proposal for a new runtime based on bolt transports that could be used by orchestrator. A spike in bolt be may be helpful but is not required.1. What is the API between it and orchestrator2. How much work will it be implementRequirements:- Should not read config file from disk- Should support multi-threading- Should accept streaming stdin of single targets to run on- It should stream events/results as ready on stdout.- keep in mind that discovery may want to use this as well. - Should not run as it's own service. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (BOLT-580) design/spike on bolt-transport api
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-580 design/spike on bolt-transport api Change By: Alex Dreyer Come up with a proposal for a new runtime based on bolt transports that could be used by orchestrator. A spike in bolt be may be helpful but is not required.1. What is the API between it and orchestrator2. How much work will it be implement Requirements:- Should not read config file from disk- Should support multi-threading- Should accept streaming stdin of single targets to run on- It should stream events/results as ready on stdout.- keep in mind that discovery may want to use this 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
Jira (BOLT-581) Evaluate top 100 modules
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-581 Evaluate top 100 modules 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-581) Evaluate top 100 modules
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-581 Evaluate top 100 modules Change By: Alex Dreyer Download the top ~100 modules on forge and examine the manifests to estimate how much code reuse "Apply from Plans" will enable.How many use bare facts or are all facts accessed through $::facts? How many include providers?How many include types?Which core types and providers are most common? How many modules just use File/Service/Exec?How many include non-autoloader manifests? IE something other than a class or defined type at top scope. Are these even allowed in puppet 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (BOLT-581) Evaluate top 100 modules
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-581 Evaluate top 100 modules Change By: David Kramer Sprint: Bolt Kanban Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-581) Evaluate top 100 modules
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-581 Evaluate top 100 modules Change By: Alex Dreyer How many of Download the top ~ 100 modules on forge and examine the manifests to estimate how much code reuse "Apply from Plans" will enable.How many use bare facts or are all facts accessed through $::facts ? How many include providers? How many include types?Which core types and providers are most common ? How many modules just use File/Service/Exec? How many include non-autoloader manifests? 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-567) POC catalog compiler
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-567 POC catalog compiler 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-566) Create syntax examples for applying manifest code from a plan
Title: Message Title David Kramer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-566 Create syntax examples for applying manifest code from a plan Change By: David Kramer Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-566) Create syntax examples for applying manifest code from a plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-566
Create syntax examples for applying manifest code from a plan
Change By:
Alex Dreyer
What options are possible for applying a manifest from puppet code without relying on heredocs or external files. The result of this ticket should be a few options that are feasible in the parse and can be user tested.Requirements1. Accepts arguments2. Accepts a chunk of inline manifest code3. Probably starts with a recognizable understandable keyword4. Should not allow nested invocationsQuestions:1. What examples do we want to use for the user test(https://github.com/puppetlabs/plan_resources/blob/master/progression/plans/two.pp)2. What non-lambda syntax do we want? we're cutting this until we hear otherwise from users. 3. How should apply_file apply work? What is the file path relative too? Is it should take a function? path to a .pp file in the modules files directory. apply('module/files/my_manifest.pp', $targets, $options)
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-566) Create syntax examples for applying manifest code from a plan
Title: Message Title David Kramer assigned an issue to Unassigned Puppet Task Runner / BOLT-566 Create syntax examples for applying manifest code from a plan Change By: David Kramer Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8723) Agent Functions - Create Vault deferred evaluation
Title: Message Title Henrik Lindberg commented on PUP-8723 Re: Agent Functions - Create Vault deferred evaluation First, I don't think we can dictate what users should be using wrt Vault authentication, they may already have Vault and may use simple user/password, tokens, or certs. We may choose to only support one of them Secondly, we need to get the secret (login, token, or login) to the agent in a safe way. We can do that with one of: a task a REST endpoint in puppet server that obtains the token. That means that each apply would hit puppet server to get the token, puppet server in turn would get it from vault. Puppet server could be logged in for a longer period of time making the calls to vault slightly more efficient (as you pointed out). For masterless operation we probably want to have a third option where the secret is fed to puppet apply via env variable. It can then be set by some command the user wants to use. A task is easy to do, but users may not want to give nodes the power to log in and ask for a token. 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-8696) Puppet loses track of the current environment
Title: Message Title Jacob Helwig commented on PUP-8696 Re: Puppet loses track of the current environment Merged to master branch in 74088badfc. 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-566) Create syntax examples for applying manifest code from a plan
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-566 Create syntax examples for applying manifest code from a plan 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-566) Create syntax examples for applying manifest code from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-566 Create syntax examples for applying manifest code from a plan Change By: Alex Dreyer What options are possible for applying a manifest from puppet code without relying on heredocs or external files. The result of this ticket should be a few options that are feasible in the parse and can be user tested.Requirements1. Accepts arguments2. Accepts a chunk of inline manifest code3. Probably starts with a recognizable understandable keyword4. Should not allow nested invocationsQuestions:1. What examples do we want to use for the user test (https://github.com/puppetlabs/plan_resources/blob/master/progression/plans/two.pp) 2. What non- module lambda syntax do we want?3. How should apply_file work? What is the file path relative too? Is it a function? 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
Jira (BOLT-566) Create syntax examples for applying manifest code from a plan
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-566 Create syntax examples for applying manifest code from a plan Change By: David Kramer Summary: Explore Create syntax options examples for applying manifest code from a plan 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-562) I want to know how many targets are present in my inventory file
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-562 I want to know how many targets are present in my inventory file Change By: Nick Lewis 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-562) I want to know how many targets are present in my inventory file
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-562 I want to know how many targets are present in my inventory file Change By: Nick Lewis Release Notes Summary: Bolt analytics now collects information about how many nodes and groups are defined in the inventory file. 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-533) Move facts to an external module
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Michael Smith Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8723) Agent Functions - Create Vault deferred evaluation
Title: Message Title Henrik Lindberg commented on PUP-8723 Re: Agent Functions - Create Vault deferred evaluation Jayant Sane We really do not need to keep the discussion about this as secrets to the community. We only need to do that if we are discussing something that is a CVE, a non open source feature, or if specific to a customer. So, I am going to summarize and comment in an open comment below this. 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-533) Move facts to an external module
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Lucy Wyman 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-566) Explore syntax options for applying manifest code from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-566 Explore syntax options for applying manifest code from a plan Change By: Alex Dreyer What options are possible for applying a manifest from puppet code without relying on heredocs or external files. The result of this ticket should be a few options that are feasible in the parse and can be user tested.Requirements1. Accepts arguments2. Accepts a chunk of inline manifest code3. Probably starts with a recognizable understandable keyword4. Should not allow nested invocationsQuestions:1. How much should it look like a function call What examples do we want to use for the user test 2. How can What non-module syntax do we limit ambiguity want? 3. How should apply_file work? What is natural for users. the file path relative too? Is it a function? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-6894) Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-6894 Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile Change By: Jacob Helwig Release Notes Summary: Updated the version of the Addressable Ruby Gem now that Ruby 1.9.3 support has been removed from Puppet. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3661) Extract zpool type/provider into a module
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-3661 Extract zpool type/provider into a module Change By: Jacob Helwig Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-566) Explore syntax options for applying manifest code from a plan
Title: Message Title Alex Dreyer commented on BOLT-566 Re: Explore syntax options for applying manifest code from a plan Henrik Lindberg see BOLT-567. Our plan is to compile the catalogs in a subprocess for now. 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-581) Evaluate top 100 modules
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-581 Evaluate top 100 modules Issue Type: Task Assignee: Unassigned Created: 2018/06/12 8:37 AM Priority: Normal Reporter: Alex Dreyer How many of the top 100 modules use bare facts? How many include providers? How many include non-autoloader manifests? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-557) Pass _task parameter to tasks
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-557 Pass _task parameter to tasks Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-566) Explore syntax options for applying manifest code from a plan
Title: Message Title
Henrik Lindberg commented on BOLT-566
Re: Explore syntax options for applying manifest code from a plan
You are right, by adding a keyword you are relatively free to do what you want after that. You are still reusing statements and parameters so it is pretty much the full language you get there. (Changing those are much harder). More work is required since the task compiler does not have a catalog and will validate all resource expressions, class definitions, etc. as errors (since the constructs are not supported). The start looks good - I noticed a few things:
There is an unused "parent" attribute in ApplyExpression
An entry is missing in "model_label_provider.rb" for ApplyExpression.
Something is probably wanted in the validator ("checker4_0.rb") - see how other things having parameters and a body are validated.
You probably want opt_statements rule as opposed to statements to make it possible to comment out the entire body of an apply (would otherwise be a syntax error).
One tricky thing is to clean up between applies - the regular compiler keeps track of if definitions have been evaluated or not, it does lazy resolution of dependencies, it validates the catalog at the end, etc. etc. (I am sure there will be other tickets for this, but maybe worth considering the consequences when designing the syntax as semantics may be affected).
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8899) New setting to allow external control over start of puppet run
Title: Message Title Matthias Hörmann commented on PUP-8899 Re: New setting to allow external control over start of puppet run Well, it would be useful if the interface to the outside world remained the same, we would want e.g. Puppet to be started by init/systemd on boot, we would want to be able to restart it the normal way (which is also one of the reasons cron is not really all that useful, nor is the splay setting),... Overall it would be nice to hide the implementation detail that avoids the concurrent Puppet runs as much as possible so we do not have to rework a variety of scripts that work on the assumption that they can trigger a Puppet run in the same way on all systems. 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-7486) useradd provider silently does not set password
Title: Message Title Josh Cooper commented on PUP-7486 Re: useradd provider silently does not set password Alan Smith ah my mistake, I was conflating provider features used in confine statements (which can delay evaluation of the resource until later in the run when the provider becomes suitable): confine :feature=> :cfpropertylist With a provider's required_feature for managing parameter/properties. This form doesn't cause resources to be deferred: newparam(:umask, :required_feature => :umask) do I agree silently ignoring it is wrong. Either the resource should be deferred (in case libshadow is installed during the run), or the manifest author should add an explicit dependency, and puppet should fail the run if it's asked to manage a property/parameter that the provider can't. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
