Jira (PUP-6741) When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Title: Message Title Moses Mendoza commented on PUP-6741 Re: When `recurse => true` is used in a file resource, tags are not applied to all recursive objects. Thanks Christian Hoffmann for this tip! After investigating too I came to the same conclusion that the cause here is effectively missing tags on the whit "sentinel" resources. Charlie Sharpsteen I believe suggested a similar thing in PUP-5777 (linked). A PR is now up against puppet Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5777) Whits don't copy tags from the containers they replace
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-5777 Whits don't copy tags from the containers they replace Change By: Charlie Sharpsteen Affects Version/s: PUP 4.8.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6934) Determine correct directory for locale files
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-6934 Determine correct directory for locale files Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6763) Make CI job to update POT files
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6763 Make CI job to update POT files Change By: Maggie Dreyer Summary: Make CI job to update PO POT files Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6763) Make CI job to update PO files
Title: Message Title Maggie Dreyer commented on PUP-6763 Re: Make CI job to update PO files In order to be consistent across projects, we are probably going to compile the PO files to MO files even for Ruby. This allows us to use a common directory structure for installation of all projects. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6763) Make CI job to update PO files
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-6763
Make CI job to update PO files
Change By:
Maggie Dreyer
In order to get translation of Puppet underway, we need CI job added to the Puppet component pipeline which does the following:* generates a PO POT file for each target language, updating existing ones as necessary * includes the original SHA in the updated PO files POT file * commits updated PO files POT file to the repo if there were changes (the resulting SHA is the one that will get promoted into puppet-agent)* notifies the Transifex server that an update has occurredThe PO files POT file can be generated via a series of rake commands command provided by the gettext gem: * first, use {{bundle exec rake gettext:pot}} to produce the template file * then, for example, {{bundle exec rake gettext:po['jp']}} will produce a Japanese PO file and place it in {{locales/jp}} inside the Puppet repo. * repeat PO file generation for each supported language The PO files generated produced by Transifex from this POT file will be copied from that directory to the correct location on the system when Puppet is installed.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6937) Puppet epp not working with parameters on version 4.8
Title: Message Title Henrik Lindberg commented on PUP-6937 Re: Puppet epp not working with parameters on version 4.8 Aha! When you are using EPP, all occurrences of <% are EPP tags and they are supposed to contain puppet logic. So, the content you have on line 111 looks like an EPP tag, and then the pipe that means "start of lambda parameters" to puppet (which then is not right in the context where it is, and why you get a syntax error). If your intent is that the rendered result should contain the actual text of line 111 - then you need to escape the tags so EPP ignores them. Like this: <%%| $x, $y, $z='this is a default value' |%%> Read more here: https://docs.puppet.com/puppet/latest/reference/lang_template_epp.html#tags I am closing this ticket, but if I misunderstood something it can be reopened. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-143) Add Windows information to Strings README
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-143 Add Windows information to Strings README Change By: Lindsey Smith Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-144) acceptance: expand matrix to include windows
Title: Message Title Eric Thompson created an issue Puppet Strings / PDOC-144 acceptance: expand matrix to include windows Issue Type: Task Assignee: Eric Thompson Created: 2016/11/23 1:17 PM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-143) Add Windows information to Strings README
Title: Message Title Jean Bond created an issue Puppet Strings / PDOC-143 Add Windows information to Strings README Issue Type: Bug Assignee: Jean Bond Components: DOCS Created: 2016/11/23 12:59 PM Priority: Normal Reporter: Jean Bond From GitHub: er0ck: does this work in windows? should we provide instructions there? whopper: It wouldn't work in Windows, and we probably should have instructions here. It's a small use case, as you'd only do this if you were authoring a module on Windows (since windows masters aren't supported, so you wouldn't be installing a bunch of modules on a windows machine). Still, some people do write modules in Windows. Add Comment
Jira (PUP-6938) ssh_authorized_key should be able to take a ready-made OpenSSH public key
Title: Message Title Mikhail T. created an issue Puppet / PUP-6938 ssh_authorized_key should be able to take a ready-made OpenSSH public key Issue Type: Improvement Assignee: Unassigned Created: 2016/11/23 12:20 PM Priority: Normal Reporter: Mikhail T. When creating adding an authorized public key with the Ssh_authorized_key-resource, the manifest is supposed to provide all of the pieces of the key. It would be very nice, if the resource could simply parse an existing foo.pub in the format used by OpenSSH (maybe, in some other formats as well). The path to the file can be interpreted the same way, source-attribute of the File-resource is or, perhaps even better, the way template() interprets its arguments. Options specified in the manifest can complement and, in case of conflict, overwrite those found in the file. By treating the keys as data rather than as code, it would be easier for users to deal with large number of them. Add Comment
Jira (FACT-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title Peter Huene commented on FACT-1538 Re: Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't Also, in retrospect this is probably the wrong behavior; Facter should either have a separate "primary" ipv6 interface or just treat the ipaddress6 fact as the first non-local address it finds on any interface, like Facter 2 did. Right now if a resolver doesn't find a primary interface, the fallback logic is to use the first interface with a non-local ipv4 or ipv6 address, which means it is possible for either one of ipaddress or ipaddress6 to be link-local provided the other is not. The Windows resolver does attempt to name the primary interface and follows the same logic: https://github.com/puppetlabs/facter/blob/master/lib/src/facts/windows/networking_resolver.cc#L201 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title Peter Huene commented on FACT-1538 Re: Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't What's the full networking fact show? Facter 3's ipaddress6 is for the "primary" interface; perhaps ipaddress is non-local and caused that interface to be treated as primary? We should probably be stripping the scope id. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2778) Issues with Cron resource type creating duplicate crons
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-2778 Issues with Cron resource type creating duplicate crons Change By: Eric Sorenson Labels: aix-parity cron customer needs_repro Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2778) Issues with Cron resource type creating duplicate crons
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-2778 Issues with Cron resource type creating duplicate crons Change By: Geoff Nichols Labels: aix-parity cron customer needs_repro Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1347) AIX user provider changes gecos field on every run if comment is ''
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1347 AIX user provider changes gecos field on every run if comment is '' Change By: Eric Sorenson Priority: Normal Trivial Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3611) Implement install_options for nim package provider
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3611 Implement install_options for nim package provider Change By: Geoff Nichols Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3611) Implement install_options for nim package provider
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3611 Implement install_options for nim package provider Change By: Geoff Nichols Acceptance Criteria: - Can pass install_options parameters to nim provider. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3611) Implement install_options for nim package provider
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3611 Implement install_options for nim package provider Change By: Eric Sorenson Priority: Normal Minor Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3611) Implement install_options for nim package provider
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3611 Implement install_options for nim package provider Change By: Eric Sorenson The NIM provider has enough divergence from other package providers that it would be helpful to have support for an install_options hash, similar to gem, pip, and windows. Original description:The NIM package provider is missing a parameter for installp_bundle.It would be very helpful in many cases to install lpp_sorces and specify with -a installp_bundle=yyy only a subset of the whole lpp_source. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3611) Implement install_options for nim package provider
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3611 Implement install_options for nim package provider Change By: Eric Sorenson The NIM provider has enough divergence from other package providers that it would be helpful to have support for an install_options hash, similar to gem, pip, and windows. Original description:The NIM package provider is missing a parameter for installp_bundle.It would be very helpful in many cases to install lpp_sorces lpp_sources and specify with -a installp_bundle=yyy only a subset of the whole lpp_source. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-1538
Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Change By:
Josh Cooper
Facter 2 skipped ipv6 link local addresses:https://github.com/puppetlabs/facter/blob/2.x/lib/facter/ipaddress6.rb#L31Facter 3 does not:{noformat}$ facter --version3.4.1 (commit d0f32490f41ca12722c13e4c48d4572ae4f9bfdc)$ facter os.nameDebian$ facter ipaddress6fe80::250:56ff:fe8f:8a0d{noformat}On Windows, the link local address has a scope ID, which ruby's IPAddr can't parse:{noformat}irb(main):013:0> require 'ipaddr'=> falseirb(main):014:0> require 'facter'=> falseirb(main):015:0> Facter.value(:ipaddress6)=> "fe80::c484:8673:8703:6b60%14"irb(main):016:0> IPAddr.new Facter.value(:ipaddress6)IPAddr::InvalidAddressError: invalid address{noformat}http://superuser.com/questions/99746/why-is-there-a-percent-sign-in-the-ipv6-addresshttps://bugs.ruby-lang.org/issues/8464As a result, the {{whereami}} fact that we use internally breaks when Facter 3 is run on Windows. /cc [~branan], [~michael.smith], [~peter.huene]
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title Josh Cooper created an issue Facter / FACT-1538 Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't Issue Type: Bug Assignee: Unassigned Created: 2016/11/23 11:20 AM Priority: Normal Reporter: Josh Cooper Facter 2 skipped ipv6 link local addresses: https://github.com/puppetlabs/facter/blob/2.x/lib/facter/ipaddress6.rb#L31 Facter 3 does not: $ facter --version 3.4.1 (commit d0f32490f41ca12722c13e4c48d4572ae4f9bfdc) $ facter os.name Debian
Jira (PUP-3611) Implement install_options for nim package provider
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3611 Implement install_options for nim package provider Change By: Eric Sorenson Summary: NIM Implement install_options for nim package provider is missing parameter for installp_bundle Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1347) AIX user provider changes gecos field on every run if comment is ''
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1347 AIX user provider changes gecos field on every run if comment is '' Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1347) AIX user provider changes gecos field on every run if comment is ''
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1347 AIX user provider changes gecos field on every run if comment is '' Change By: Geoff Nichols Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1347) AIX user provider changes gecos field on every run if comment is ''
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1347 AIX user provider changes gecos field on every run if comment is '' Change By: Geoff Nichols Acceptance Criteria: - Can set an empty comment field. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5577) confine :exists => "/run/systemd/system" breaks chroot installation
Title: Message Title Sven Mueller commented on PUP-5577 Re: confine :exists => "/run/systemd/system" breaks chroot installation Not sure if I should re-open this issue or create a new one: The check for /run/systemd/system also breaks management of services in Debian chroots (such as the debootstrap chroot created during installations from debian-installer - in which we run Puppet for the first time during automated installations). The problem is that it checks for a running systemd, it doesn't check for systemd to be in use by the given system. The proper check to see if systemd is used on a given system would be to check if /sbin/init is a link to /lib/systemd/systemd Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6188) Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-6188 Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings Change By: Moses Mendoza Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6188) Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings
Title: Message Title Moses Mendoza commented on PUP-6188 Re: Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings this passed CI at https://jenkins.puppetlabs.com/job/platform_puppet-agent_intn-van-sys-pez-multi_daily-pa-master/74/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6937) Puppet epp not working with parameters on version 4.8
Title: Message Title Mihail Mihaylov commented on PUP-6937 Re: Puppet epp not working with parameters on version 4.8 Hello Henrik, Thank you for the prompt reply. This is line 111 exactly: <% | $x, $y, $z='this is a default value' | %> I am sure that the issue is with the pipe character "|", however, I am not sure why. Another think I should have mentioned is that the template is actually a python scrupt. I have renamed a working python script from memcached.py to memcached.epp so that it is a template. The script begins with: " #!/usr/bin/env python " as every python script. I suspect that this may cause a problem somehow.. maybe the parser is thinking that "<%-| " is not a valid python syntax or something like that. Do you have any ideas? Thanks, Mihail Mihaylov Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
