Jira (PUP-9007) Follow directory symlinks under manifest tree.
Title: Message Title Henrik Lindberg assigned an issue to Patrice Levesque Puppet / PUP-9007 Follow directory symlinks under manifest tree. Change By: Henrik Lindberg Assignee: Patrice Levesque 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-9007) Follow directory symlinks under manifest tree.
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9007 Follow directory symlinks under manifest tree. Change By: Henrik Lindberg Assignee: Patrice Levesque 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-9007) Follow directory symlinks under manifest tree.
Title: Message Title Henrik Lindberg commented on PUP-9007 Re: Follow directory symlinks under manifest tree. I don't think we want this. The mechanism (directory of files instead of import) has been there for several years now, and most users have been able to transition to more modern puppet without having to use symlinks. (The choice of not supporting symlinks was deliberate). The primary use case for directory structure is for node classification using the node _expression_ and to be able to have groups of different nodes in one .pp file (or one .pp file per node). This is much better solved by using an ENC or by using hiera to classify nodes, and to let that drive inclusion of classes that are autoloaded (neither requires the use of a master). Not want you want to hear, but: Maybe it is time to bite the bullet and convert the code base to a typical usage pattern of modern puppet? Since the use of symlinks is far from best practice I am quite reluctant to add support for it. Maybe I am overly protective of users that will use this to get into trouble, or maybe I am just grumpy today so asking for second opinions - ping Eric Thompson Eric Sorenson. 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-9007) Follow directory symlinks under manifest tree.
Title: Message Title Patrice Levesque commented on PUP-9007 Re: Follow directory symlinks under manifest tree. Maybe it is time to bite the bullet and convert the code base to a typical usage pattern of modern puppet? Well that's the end goal, but I have my hands full already with the changes in variable scoping inside templates, class names that will not accept dashes in their name anymore, the exclusion of import, and probably other boring adjustments I'll encounter on the way. Maybe I am overly protective of users that will use this to get into trouble Bind mounts, directory hard links and monkey-patching the Puppet::Node::Environment::perform_initial_import method are three more ways I can see around that “protection”. I'd rather not use them, and they make usage of symlinks look like a lesson in elegance 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-1541) Separate out hold state into a separate property
Title: Message Title Barraj commented on PUP-1541 Re: Separate out hold state into a separate property This ticked is important as it may lead to a solution for the old famous Bug #1720 (in the old tracking site https://projects.puppetlabs.com/issues) : The package resource type doesn't notice installed packages when more than one is installed 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-706) Puppet Bolt v: 0.21.3 - header field value cannnot include CR/LF
Title: Message Title
Clodonil H Trigo created an issue
Puppet Task Runner / BOLT-706
Puppet Bolt v: 0.21.3 - header field value cannnot include CR/LF
Issue Type:
Bug
Affects Versions:
BOLT 0.21.2
Assignee:
Unassigned
Components:
Tasks
Created:
2018/07/18 5:34 AM
Fix Versions:
0.21.3
Priority:
Normal
Reporter:
Clodonil H Trigo
Hi, I run bolt task in vagrant lab in pcp Transport and return of result: [root@devops .puppetlabs]# bolt task run exemplo1::exe1 --nodes pcp://node1.vm Started on node1.vm... Failed on node1.vm: header field value cannnot include CR/LF Failed on 1 node: pcp://node1.vm Ran on 1 node in 0.09 seconds Run in debug mode: [root@devops .puppetlabs]# bolt task run exemplo1::exe1 --nodes pcp://node1.vm --debug Loaded inventory from /root/.puppetlabs/bolt/inventory.yaml Did not find config for pcp://node1.vm in inventory Submitting analytics: { "v": 1, "cid": "94f3c8cf-a14a-4ff5-8f2b-20f615d99abd", "tid": "UA-120367942-1", "an": "bolt", "av": "0.21.3", "aip": true, "ul": "en-US", "cd1": "CentOS 7", "t": "screenview", "cd": "task_run", "cd5": "human", "cd4": 1, "cd2": 0, "cd3": 1 } Completed analytics submission ModuleLoader: module 'aggregate' has unknown dependencies - it will have all other modules visible ModuleLoader: module 'canary' has unknown dependencies - it will have all other modules visible ModuleLoader: module 'facts' has unknown dependencies - it will have all other modules visible ModuleLoader: module 'puppetdb_fact' has unknown dependencies - it will have all other modules visible Started with 100 max thread(s) ModuleLoader: module
Jira (BOLT-698) Output of ruby script over WinRM not consistent
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-698 Output of ruby script over WinRM not consistent Change By: Michael Smith 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-705) Performance regression in command/script running from analytics collection
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-705
Performance regression in command/script running from analytics collection
Change By:
Michael Smith
Release Notes Summary:
Slow down in the last release for 'command run' and 'script run' has been fixed.
Summary:
Refactor reporting bundled content to GA Performance regression in command/script running from analytics collection
Release Notes:
Bug Fix
Issue Type:
Improvement Bug
Preliminary testing seemed to indicate that performance impact of initializing pal with an "empty" config to generate a list of bundled content would be negligible. In practice the performance impact is unacceptable , particularly on {{command run}} and {{script run}}.Instead of *always* building a list of bundled content, only do so when running a task or plan.
Add Comment
Jira (BOLT-699) --boltdir option should set Boltdir rather than config file
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-699 --boltdir option should set Boltdir rather than config file Change By: Michael Smith 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-705) Performance regression in command/script running from analytics collection
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-705 Performance regression in command/script running from analytics collection Change By: Michael Smith 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-699) --boltdir option should set Boltdir rather than config file
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-699 --boltdir option should set Boltdir rather than config file Change By: Michael Smith Release Notes Summary: The '--boltdir' option now works correctly to set the directory where default config, inventory, and modulepath are found. 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 (BOLT-705) Performance regression in command/script running from analytics collection
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-705 Performance regression in command/script running from analytics collection Change By: Michael Smith Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8985) manage_internal_file_permissions should default to the new packaging default
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8985 manage_internal_file_permissions should default to the new packaging default Change By: Geoff Nichols Sprint: Windows 2018-07-11, Windows 2018-07-18 , Windows 2018-07-25 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 Geoff Nichols updated an issue Puppet / PUP-8939 Administrators are not able to run puppet agent when installed as SYSTEM in some cases Change By: Geoff Nichols Sprint: Windows 2018-07-18 , Windows 2018-07-25 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-8793) Package module into puppet-agent
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8793 Package module into puppet-agent Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8791) Create the CI pipeline
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8791 Create the CI pipeline Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8795) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8795 Move all outstanding PUP tickets to Modules Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8794) Remove type/provider code from puppet
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8794 Remove type/provider code from puppet Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8792) Release 1.0.0 to the forge
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8792 Release 1.0.0 to the forge Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8791) Create the CI pipeline
Title: Message Title Melissa Stone commented on PUP-8791 Re: Create the CI pipeline PR at https://github.com/puppetlabs/ci-job-configs/pull/4775 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-8790) Extract the code & verify the module
Title: Message Title Melissa Stone commented on PUP-8790 Re: Extract the code & verify the module PR at https://github.com/puppetlabs/puppetlabs-k5login_core/pull/1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8794) Remove type/provider code from puppet
Title: Message Title Melissa Stone commented on PUP-8794 Re: Remove type/provider code from puppet PR at https://github.com/puppetlabs/puppet/pull/6931 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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled
Title: Message Title Enis Inan updated an issue Facter / FACT-1475 facter returns wrong ipv6 information when IPV6 stack is disabled Change By: Enis Inan Sprint: Platform OS 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-1475) facter returns wrong ipv6 information when IPV6 stack is disabled
Title: Message Title Enis Inan assigned an issue to Enis Inan Facter / FACT-1475 facter returns wrong ipv6 information when IPV6 stack is disabled Change By: Enis Inan Assignee: Enis Inan 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-8811) Extract the code & verify the module
Title: Message Title Melissa Stone commented on PUP-8811 Re: Extract the code & verify the module PR at https://github.com/puppetlabs/puppetlabs-mount_core/pull/1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters
Title: Message Title
James Ralston commented on PUP-8947
Re: Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters
The problem I have with using covert_to in lookup_options is that is completely falls down in a case like this:
class duo (
Struct[{
Optional['duo'] => Struct[{
Optional['host'] => Optional[String],
Optional['ikey'] => Optional[Sensitive[String]],
Optional['skey'] => Optional[Sensitive[String]],
Optional['groups']=> Optional[Variant[String, Array[String]]],
Optional['failmode'] => Optional[Enum['safe', 'secure']],
Optional['pushinfo'] => Optional[Variant[Boolean, Enum['yes', 'no']]],
Optional['http_proxy']=> Optional[String],
Optional['autopush'] => Optional[Variant[Boolean, Enum['yes', 'no']]],
Optional['prompts'] => Optional[Integer[1,default]],
Jira (PDB-3975) (maint) Add flexibility for the puppetserver hostname
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3975 (maint) Add flexibility for the puppetserver hostname Issue Type: Bug Assignee: Unassigned Created: 2018/07/18 11:38 AM Priority: Normal Reporter: gepetto-bot 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://gr
Jira (BOLT-565) Apply from Plans
Title: Message Title Michael Smith commented on BOLT-565 Re: Apply from Plans Reference docs: https://docs.google.com/document/d/1BflcENVA1hVfJU55gofxNA4YnZsQNlf6NjKixIj_HM8/edit?usp=sharing 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-9009) The zypper and rpm providers have duplicate instance lists
Title: Message Title Jarret Lavallee created an issue Puppet / PUP-9009 The zypper and rpm providers have duplicate instance lists Issue Type: Bug Affects Versions: PUP 5.5.3 Assignee: Unassigned Components: Types and Providers Created: 2018/07/18 11:55 AM Environment: PE 2018.1.2 with SLES nodes and Package inventory collection enabled. Labels: cspapercuts Priority: Normal Reporter: Jarret Lavallee Problem PE package inventory shows duplicate packages for the rpm and zypper providers on SLES. Expected behavior PE package inventory shows one copy of the package. This behavior is seen on EL, but not SLES. What we think is happening The zypper provider for the package resource inherits from the rpm provider, but does not specify it as the :source. This results in both zypper and rpm being returned by the providers_by_source method. The result is that PE package inventory shows duplicate packages for these two providers on SLES. The zypper provider: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/zypper.rb#L1 This behavior is not seen on RHEL as the yum provider has rpm as a :source. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L1 Questions What are risks of setting :source => :rpm in the zypper provider?
Jira (PUP-8811) Extract the code & verify the module
Title: Message Title Melissa Stone commented on PUP-8811 Re: Extract the code & verify the module Merged to master at https://github.com/puppetlabs/puppetlabs-mount_core/commit/1a48e4309721509f75a076d80036aef0432be6f4 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-8812) Create the CI pipeline
Title: Message Title Melissa Stone commented on PUP-8812 Re: Create the CI pipeline Merged into master with https://github.com/puppetlabs/ci-job-configs/commit/6956323895da0095838a75b5c6bab2d154b626a7 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-3976) mergeup 5.1.x -> 5.2.x
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3976 mergeup 5.1.x -> 5.2.x Issue Type: Bug Assignee: Unassigned Created: 2018/07/18 1:21 PM Priority: Normal Reporter: gepetto-bot 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-bug
Jira (BOLT-698) Output of ruby script over WinRM not consistent
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-698 Output of ruby script over WinRM not consistent Change By: Michael Smith 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-7561) Event with 'failure' status should be created when a service fails to restart
Title: Message Title Josh Cooper commented on PUP-7561 Re: Event with 'failure' status should be created when a service fails to restart Closing as a dup of PUP-8908. If a service fails to restart, we now record failed_to_restart: true for the resource, and there is an event with status: failed: Service[my_service]: title: my_service file: "/etc/puppetlabs/code/modules/service_restart_failure/manifests/init.pp" line: 30 resource: Service[my_service] resource_type: Service provider_used: init containment_path: - Stage[main] - Service_restart_failure - Service[my_service] evaluation_time: 0.008648017 tags:
Jira (PDB-3977) Merge 5.2.x to master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3977 Merge 5.2.x to master Issue Type: Bug Assignee: Unassigned Created: 2018/07/18 3:01 PM Priority: Normal Reporter: gepetto-bot 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
Jira (PDB-3978) Merge 5.1.x into 5.2.x
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3978 Merge 5.1.x into 5.2.x Issue Type: Bug Assignee: Unassigned Created: 2018/07/18 3:03 PM Priority: Normal Reporter: gepetto-bot 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-bug
Jira (PUP-8816) Move all outstanding PUP tickets to Modules
Title: Message Title Josh Cooper commented on PUP-8816 Re: Move all outstanding PUP tickets to Modules Done: https://tickets.puppetlabs.com/browse/MODULES-7510?jql=project%20%3D%20MODULES%20AND%20resolution%20%3D%20Unresolved%20and%20component%20in%20(mount_core) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8794) Remove type/provider code from puppet
Title: Message Title Josh Cooper commented on PUP-8794 Re: Remove type/provider code from puppet Merged to puppet#master in https://github.com/puppetlabs/puppet/commit/ca56914d7aeb777cc06ac7fa7638f7119d01ff8e Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7551) deprecate 'puppet describe'
Title: Message Title Josh Cooper commented on PUP-7551 Re: deprecate 'puppet describe' Moving this to needs information pending discussion about improvements to puppet-strings 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-8947) Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters
Title: Message Title
Henrik Lindberg commented on PUP-8947
Re: Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters
James Ralston For the issue you just showed I think we could consider making convert_to to perform type casting from a Struct with non Sensitive values to one having Sensitive entries. The first workaround is to make the entire hash be Sensitive. The second workaround I can think if is to have the two sensitive values be included in the hash (in hiera) via aliasing to two separate keys with the use of convert_to: 'Sensitive' for those two keys. Third option (not so much a workaround) is to update the json and yaml backend functions so that they accept an option rich_data=true that would read a json/yaml file and interpret the format of the data as having our rich-data encoding. In puppet 6.0 that would mean you can write a Sensitive value directly in a data file:
pam::pam_duo_conf:
duo:
ikey:
__ptype: 'Sensitive'
__pvalue: 'the secret key'
...
Fourth option - support a .pp datafile backend function: it would simply read a .pp file as data - for example containing:
{pam::pam_duo_conf => { duo => { ikey => 'secret key' }}}
Fifth option: Write a small backend function to return the structs that contain Sensitive data elements. (You can easily do this yourself). It gets a bit complicated if a Sensitive[Hash] returned that way should merge with other sensit
Jira (BOLT-698) Output of ruby script over WinRM not consistent
Title: Message Title Michael Smith commented on BOLT-698 Re: Output of ruby script over WinRM not consistent https://gist.github.com/MikaelSmith/4c1a9fd6e9b1b69ccca0afacc27b594a contains the simplest reproduction I've come up with. As far as I can tell, trying to use events to capture stdout and stderr doesn't provide us a guaranteed order for any of the events. Which really messes with output if we're printing pretty-formatted JSON. 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-698) Output of ruby script over WinRM not consistent
Title: Message Title Michael Smith commented on BOLT-698 Re: Output of ruby script over WinRM not consistent I'm not sure what to do about it. All solutions that distinguish between stdout and stderr use the event-based solution, or require relatively recent versions of .NET Framework (4.5+). 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-3979) Merge 5.2.x into master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3979 Merge 5.2.x into master Issue Type: Bug Assignee: Unassigned Created: 2018/07/18 3:47 PM Priority: Normal Reporter: gepetto-bot 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-bu
Jira (BOLT-682) Have nice error message if user tries 'apply' with no PA
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-682 Have nice error message if user tries 'apply' with no PA Change By: Michael Smith 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-8814) Package module into puppet-agent
Title: Message Title Josh Cooper commented on PUP-8814 Re: Package module into puppet-agent Merged to puppet-agent#master in https://github.com/puppetlabs/puppet-agent/commit/51dad1850040f3c1841ea07d5374264a8aec80e1 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.
