Jira (PUP-4725) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund assigned an issue to Eric Sorenson Puppet / PUP-4725 Prepare long form release notes and short form release story Change By: Nicholas Fagerlund Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4731) Docs pushed
Title: Message Title Nicholas Fagerlund assigned an issue to Nicholas Fagerlund Puppet / PUP-4731 Docs pushed Change By: Nicholas Fagerlund Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4636) Manifest with future parser code fails in a non-production environment with environment.conf parser=future setting
Title: Message Title Nicholas Fagerlund commented on PUP-4636 Re: Manifest with future parser code fails in a non-production environment with environment.conf parser=future setting Should this really have 4.2.0 included in the fixVersions, or should it just be 3.8.1? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4725) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on PUP-4725 Re: Prepare long form release notes and short form release story Eric Sorenson Oh hey, good call! I agree, will do. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-397) Default hierarchy was never updated per HI-374
Title: Message Title Nicholas Fagerlund created an issue Hiera / HI-397 Default hierarchy was never updated per HI-374 Issue Type: Bug Affects Versions: HI 3.0.0 Assignee: Unassigned Created: 2015/06/22 3:41 PM Priority: Blocker Reporter: Nicholas Fagerlund HI-374 was about changing two things: the default hierarchy, and the default datadir for the yaml and json backends. Both of those things were represented in two places: the actual coded defaults, and the default hiera.yaml file laid down by the installer. ext/hiera.yaml was updated, and the coded defaults were changed for the datadir, but the coded hierarchy defaults were left untouched and the default hierarchy is still common. This should block any public release of 3.0.x. Add Comment
Jira (HI-396) Hiera CLI can't check data for a node using new default hierarchy
Title: Message Title Nicholas Fagerlund created an issue Hiera / HI-396 Hiera CLI can't check data for a node using new default hierarchy Issue Type: Bug Affects Versions: HI 3.0.0 Assignee: Unassigned Created: 2015/06/22 1:47 PM Priority: Normal Reporter: Nicholas Fagerlund The new default hierarchy includes the ::trusted.certname variable, which is a member of a hash. The Hiera CLI provides no way to specify non-string variables as part of the command, since it uses a kind of nave regex to parse variables: ARGV.each do |arg| if arg =~ /^(.+?)=(.+?)$/ options[:scope][$1] = $2
Jira (FACT-1013) Scrub Jira tix for Release Notes field
Title: Message Title Nicholas Fagerlund assigned an issue to Michael Smith Facter / FACT-1013 Scrub Jira tix for Release Notes field Change By: Nicholas Fagerlund Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-58) Migrate Existing Data doesn't render properly in the Index
Title: Message Title Nicholas Fagerlund commented on PDB-58 Re: Migrate Existing Data doesn't render properly in the Index Haha oh RIGHT, I forgot I totally fixed this. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4131) Gem version specifiers are not idempotent
Title: Message Title Nicholas Fagerlund commented on PUP-4131 Re: Gem version specifiers are not idempotent This ticket's description needs love. Can someone update it with the previous behavior, how it differed from expected behavior, and how it was resolved? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4521) Pass agent-requested environment to external node classifiers
Title: Message Title Nicholas Fagerlund commented on PUP-4521 Re: Pass agent-requested environment to external node classifiers Also: Is there any user-facing impact of this new feature? (That's kind of a different question than the API one, since almost nothing but Puppet currently uses the node or catalog endpoints.) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1014) Script for generating per-fact docs from schema
Title: Message Title Nicholas Fagerlund assigned an issue to Nicholas Fagerlund Facter / FACT-1014 Script for generating per-fact docs from schema Change By: Nicholas Fagerlund Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1014) Script for generating per-fact docs from schema
Title: Message Title Nicholas Fagerlund commented on FACT-1014 Re: Script for generating per-fact docs from schema I'll give it a try! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4521) Pass agent-requested environment to external node classifiers
Title: Message Title Nicholas Fagerlund commented on PUP-4521 Re: Pass agent-requested environment to external node classifiers It sounds as though this changed Puppet's HTTPS API. Right? Or am I misunderstanding? If this changed the HTTPS API, the docs (and possibly the schemas?) in the api directory in the Puppet source must be updated. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4131) Gem version specifiers are not idempotent
Title: Message Title Nicholas Fagerlund commented on PUP-4131 Re: Gem version specifiers are not idempotent Josh Cooper What does that mean, is idempotent? I think you might mean one of the following, but I can't tell which: It will install the latest version that matches that specifier, and will be in sync if that latest-within-spec version is currently installed. If any version that matches the specifier is installed, it will be in sync. Multiple machines may drift freely and have different versions installed, if they stay within the spec. If the version isn't in sync, Puppet will install ??? version of the gem. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4521) Pass agent-requested environment to external node classifiers
Title: Message Title Nicholas Fagerlund commented on PUP-4521 Re: Pass agent-requested environment to external node classifiers OK. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4740) Add missing query parameters to Puppet HTTPS API docs
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4740 Add missing query parameters to Puppet HTTPS API docs Issue Type: Bug Assignee: Unassigned Created: 2015/06/10 3:45 PM Priority: Normal Reporter: Nicholas Fagerlund The API docs (at api/doc in the Puppet source) are missing some query parameters that are used by puppet agent in some requests. The ones I know about are source_permissions and configured_environment (see PUP-4521 ). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title Nicholas Fagerlund commented on PUP-4698 Re: Make fqdn_rand() Return A Numeric Instead of a String What other functions were never updated to return proper numbers? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4698) Make fqdn_rand() Return A Numeric Instead of a String
Title: Message Title Nicholas Fagerlund commented on PUP-4698 Re: Make fqdn_rand() Return A Numeric Instead of a String In most cases, the documentation for an obvious bug is its jira ticket. I don't believe this one is a special case. When we fix it, it'll go in the release notes. I too vote that this isn't semver breaking; it's a basic regression from 3.x. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Nicholas Fagerlund commented on HI-374 Re: Update hiera defaults to reflect current best practices Hiera 3 requires Puppet 4+, roger that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4536) Investigate and document differences between Ruby 1.9 and 2.1
Title: Message Title Nicholas Fagerlund commented on PUP-4536 Re: Investigate and document differences between Ruby 1.9 and 2.1 Do module authors have good ways to test on both of these Ruby versions? I actually don't have a good grip on the capabilities of systems like Beaker. If it's only feasible to test on 2.1, I have a problem with telling people this. Otherwise, sure. I'm not sure yet where we should be putting this information. There's not an easy slot in the docs to drop it into. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4648) Problem of indentation with epp()
Title: Message Title Nicholas Fagerlund commented on PUP-4648 Re: Problem of indentation with epp() Henrik Lindberg Thank you, that will be helpful. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4675) Output from puppet describe ssh_authorized_key is jumbled
Title: Message Title Nicholas Fagerlund commented on PUP-4675 Re: Output from puppet describe ssh_authorized_key is jumbled whoa, wtf? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4675) Output from puppet describe ssh_authorized_key is jumbled
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4675 Output from puppet describe ssh_authorized_key is jumbled Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4675) Output from puppet describe ssh_authorized_key is jumbled
Title: Message Title Nicholas Fagerlund commented on PUP-4675 Re: Output from puppet describe ssh_authorized_key is jumbled Unassigning because I have no idea why it's doing that and it doesn't appear to be a writing problem. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4675) Output from puppet describe ssh_authorized_key is jumbled
Title: Message Title Nicholas Fagerlund commented on PUP-4675 Re: Output from puppet describe ssh_authorized_key is jumbled Also, I'm gonna take the DOCS component off, because this ticket doesn't affect the content of our documentation, it just relates to a piece of code that sometimes displays docs. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4675) Output from puppet describe ssh_authorized_key is jumbled
Title: Message Title Nicholas Fagerlund assigned an issue to Unassigned Puppet / PUP-4675 Output from puppet describe ssh_authorized_key is jumbled Change By: Nicholas Fagerlund Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4675) Output from puppet describe ssh_authorized_key is jumbled
Title: Message Title Nicholas Fagerlund assigned an issue to Unassigned Puppet / PUP-4675 Output from puppet describe ssh_authorized_key is jumbled Change By: Nicholas Fagerlund Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Nicholas Fagerlund commented on HI-374
Re: Update hiera defaults to reflect current best practices
Ping. Since Hiera 2 only ships with Puppet versions that have $trusted enabled by default, let's stop using the insecure $clientcert variable. The hierarchy should include
certname/%{::trusted.certname}
instead.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4534) Specify EPP templating language
Title: Message Title Nicholas Fagerlund assigned an issue to Henrik Lindberg Puppet / PUP-4534 Specify EPP templating language Change By: Nicholas Fagerlund Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4662) EPP template can't explicitly access top scope variables if there's no node definition in the scope chain
Title: Message Title
Nicholas Fagerlund created an issue
Puppet / PUP-4662
EPP template can't explicitly access top scope variables if there's no node definition in the scope chain
Issue Type:
Bug
Assignee:
Unassigned
Components:
Language
Created:
2015/05/27 4:32 PM
Priority:
Normal
Reporter:
Nicholas Fagerlund
If you try to explicitly access a top scope variable that is shadowed by a template parameter, Puppet will incorrectly use the parameter value instead unless there's a node scope present in the scope chain.
Manifest:
$testvar = from top scope
node 'magpie.lan' {
Jira (PUP-4650) cron resources with the same name but for different users can't be purged
Title: Message Title Nicholas Fagerlund commented on PUP-4650 Re: cron resources with the same name but for different users can't be purged Hmm... I'd say that falls under DOC-1142. I think the embedded docs for the resources type is terse enough that we probably shouldn't be filling in every edge case; that's more work for a guide-style page. But I might reconsider. On the code side, though, this sounds to me that cron oughtta have a compound namevar the same way package now does. Right? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4650) cron resources with the same name but for different users can't be purged
Title: Message Title Nicholas Fagerlund assigned an issue to Unassigned Puppet / PUP-4650 cron resources with the same name but for different users can't be purged Change By: Nicholas Fagerlund Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4576) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on PUP-4576 Re: Prepare long form release notes and short form release story Ah, you're right. I hadn't noticed the deal with multi-var assignments et al when I wrote that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4582) Docs pushed
Title: Message Title Nicholas Fagerlund commented on PUP-4582 Re: Docs pushed We'll be pushing release notes on tuesday, but we may or may not be prepared to push edits to the future parser docs. Those are prioritized below getting the 4.1 docs into final shape. See DOC-1913 for details. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4576) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on PUP-4576 Re: Prepare long form release notes and short form release story Release notes are in the puppet3.8.1 branch on puppetlabs/puppet-docs, and ready to merge. Here's the short story: Puppet 3.8.1 is a bug fix release (with future parser changes) in the Puppet 3.8 series. It's the first official open source release in the 3.8 series. The main focus of this release is to align the future parser with the Puppet language as of Puppet 4.1. It also fixes several bugs. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-992) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on FACT-992 Re: Prepare long form release notes and short form release story short story: Facter 2.4.4 is a bug fix release in the Facter 2.4 series. It also deprecates the `--puppet` command line option, since it caused circular load dependencies. To run Facter in Puppet's context, you should use the `puppet facts` command instead. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-992) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on FACT-992 Re: Prepare long form release notes and short form release story Okay, those release notes were super easy. Went ahead and pushed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4630) auth.conf's `deny` directive is messed up, and allows forbidden requests according to moon phase
Title: Message Title Nicholas Fagerlund commented on PUP-4630 Re: auth.conf's `deny` directive is messed up, and allows forbidden requests according to moon phase Okay, after some testing I have a rough hypothesis. If an ACL includes the exact directive allow *, all deny rules get ignored. Otherwise, there's some kind of nasty interaction between two principles: deny goes first, and sort by level of specificity. I can't figure out exactly what the levels of specificity are... but it looks like there's only two? That is, .lan and .fakepie.lan and /\w+\.fakepie\.lan all seem to be the same level, and it'll process denies first. But if you specify a name with no globbing or regex (bishop.fakepie.lan), an allow can override a deny at the lower level. ...So I guess you could unify this and say that there are three levels of specificity, and * is the most specific. I hate this file so much. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4592) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund commented on PUP-4592 Re: Prepare long form release notes and short form release story Release notes are in the branch and ready to ship. For short story, I've got: 4.1.0 is a feature release in the Puppet 4 series. This release's main focus was improvements to the Puppet language, but it also includes some improvements to resource types and a few miscellaneous fixes. Also notable in this release: we're officially deprecating Rack and WEBrick-based Puppet master servers. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4630) auth.conf's `deny` directive is messed up, and allows forbidden requests according to moon phase
Title: Message Title Nicholas Fagerlund moved an issue Puppet / PUP-4630 auth.conf's `deny` directive is messed up, and allows forbidden requests according to moon phase Change By: Nicholas Fagerlund Workflow: Documentation ScrumTeam Workflow Key: DOC PUP - 2007 4630 Project: Documentation[Internal] Puppet Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4613) Unclear language in the spec around types being assignable from types
Title: Message Title Nicholas Fagerlund commented on PUP-4613 Re: Unclear language in the spec around types being assignable from types Henrik Lindberg Okay, so it sounds to me like Type T is assignable from type T2 means the exact same thing as Type T is a superset of type T2. Is that accurate, or am I missing a subtlety? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3512) Require metric id in Puppet Profiler API
Title: Message Title Nicholas Fagerlund commented on PUP-3512 Re: Require metric id in Puppet Profiler API Christopher Price Thank you! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title Nicholas Fagerlund commented on PUP-4483 Re: Add NotUndef type to the set of Puppet types Yeah, that's probably a good approach. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3512) Add deprecation warning for old profiler API in Puppet
Title: Message Title Nicholas Fagerlund commented on PUP-3512 Re: Add deprecation warning for old profiler API in Puppet Christopher Price or Kenneth Barber, it looks like the description of this ticket isn't accurate, and we actually removed this API completely. Is that right? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references Lookup of a parameter that at the time of accessing it has no value depends on if the resource type is a user defined or not, and if the attribute is a meta parameter, or if the value That still makes it sound like metaparameters are handled differently. Lookup of a parameter that at the time of accessing it has no value depends on _if the resource type is a user defined or not,_ and if the attribute is a meta parameter, or if the value ... If a parameter is not explicitly set, a default value is returned if a user defined type's parameter has a default value _expression_, or... These two parts still make it sound like defined resource types are handled differently, and that their default values in the parameter list have some effect, which I showed isn't true. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund assigned an issue to Henrik Lindberg Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Nicholas Fagerlund Assignee: NicholasFagerlund HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title Nicholas Fagerlund commented on PUP-4483 Re: Add NotUndef type to the set of Puppet types Can you please update the description to include the fact that Optional's behavior has changed? The examples for struct look good, thanks. The part about extracting a non-empty string from a type looks difficult to explain to users, though. (I understand it, it's just squirrelly.) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title Nicholas Fagerlund commented on PUP-4483 Re: Add NotUndef type to the set of Puppet types It also appears that the behavior of the Optional type may have changed, since it can take something other than a Type as its parameter now? Or has it always been able to do that? Is there a ticket for this change to Optional (if it was a change)? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4359) puppetversion fact is missing
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-4359
puppetversion fact is missing
Change By:
Nicholas Fagerlund
Executingpuppetwithcfacterandstdlibgeneratesanerroreverytimepuppetruns:{noformat}[root@jaiuwwlivqmy8by~]#puppet--version4.0.0-rc1[root@jaiuwwlivqmy8by~]#facter--version2.4.2[root@jaiuwwlivqmy8by~]#cfacter--version0.4.0(commitf4eecdfa9ff69c801bfedba3fc0fd5285e86b3c5)[root@jaiuwwlivqmy8by~]#facterpuppetversion4.0.0-rc1[root@jaiuwwlivqmy8by~]#cfacterpuppetversion[root@jaiuwwlivqmy8by~]#timepuppetagent-t--server$(facterfqdn)--cfacter--traceInfo:RetrievingpluginfactsInfo:RetrievingpluginInfo:LoadingfactsError:Facter:errorwhileresolvingcustomfactpe_version:undefinedmethod`match'fornil:NilClassbacktrace:/opt/puppetlabs/puppet/cache/lib/facter/pe_version.rb:13:in`block(2levels)intop(required)'/opt/puppetlabs/puppet/cache/lib/facter/pe_version.rb:20:in`call'/opt/puppetlabs/puppet/cache/lib/facter/pe_version.rb:20:in`value'/opt/puppetlabs/puppet/cache/lib/facter/pe_version.rb:20:in`block(2levels)intop(required)'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/facter.rb:27:in`call'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/facter.rb:27:in`to_hash'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/facter.rb:27:in`find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in`find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer/fact_handler.rb:15:in`find_facts'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer/fact_handler.rb:31:in`facts_for_uploading'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:97:in`get_facts'{noformat}Theerroroccursbecausecfacterdoesn'tdefinethe{{puppetversion}}fact,whichcausesstdlibissues:{code:ruby}pe_ver=Facter.value(puppetversion).match(/PuppetEnterprise(\d+\.\d+\.\d+)/){code}Itmakessenseforcfactertonotgeneratethe{{puppetversion}}factwhenrunstandalone(becausewedon'twantacyclicdependency).ButIwouldthinkpuppetwouldinjectits{{puppetversion}}intofacter(whicheverimplementationisbeingused),sothatthefactispresentduringfactresolutionandlatercompilation.Soarguablythisisapuppetissue,butmayaffectthefacter/cfacterinterface?riskassessment:highprobability:high(PErequires)severity:hightestlayer:unit h3.Resolution:Puppetnowaddsthepuppetversionfactifit'susingcfacter.
Add Comment
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title Nicholas Fagerlund commented on PUP-4483 Re: Add NotUndef type to the set of Puppet types Did this ticket incorporate the changes to the Struct type? I can't understand what those changes were from the description given. Can someone involved in writing these changes please add some examples showing the changes to the Struct type? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund assigned an issue to Henrik Lindberg Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Nicholas Fagerlund Assignee: NicholasFagerlund HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references If a parameter is not explicitly set, a default value is returned if a user defined type's parameter has a default value _expression_, or if there is a Resource Defaults _expression_ that defines a default value. Henrik Lindberg The first part, about defined resource types, is wrong. Demonstration here. The second part is right, but the spec should mention that THAT's evaluation-order dependent as well, since resource default statements usually ignore evaluation order. The part about metaparameters is unclear. You state that they behave differently, but your description of the behavior sounds like how other attributes work (i.e. only an explicitly set value can be accessed). What's actually different? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4613) Unclear language in the spec around types being assignable from types
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4613 Unclear language in the spec around types being assignable from types Issue Type: Bug Assignee: Unassigned Created: 2015/05/14 11:32 AM Labels: specification Priority: Normal Reporter: Nicholas Fagerlund In the types page in the spec, we sometimes see language like: NotUndef; a type that represents all types not assignable from the Undef type I don't understand what this means, and the page doesn't give me anything that would help me grab onto it. What does it mean to assign a type from a type? What does it mean to assign a type from, or to, something other than a type? Is there some less opaque way this could be phrased, to make the spec more usable? Or if not, can some definitions be added? Add Comment
Jira (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title Nicholas Fagerlund commented on PUP-4193 Re: Add pattern matching to the Puppet DSL Henrik Lindberg So even though the splat operator isn't used here, control expressions always behave as though they're having the splat operator applied to them? Am I understanding that right? And is that behavior new? What effect does that behavior have when the cases are NOT lambdas? Or are control expressions only implicitly splatted when cases are lambdas? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title Nicholas Fagerlund commented on PUP-4193 Re: Add pattern matching to the Puppet DSL It looks as though the summary (title) of this ticket is out of date, and does not describe the work that was actually done. Can someone please update the summary? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title Nicholas Fagerlund commented on PUP-4193 Re: Add pattern matching to the Puppet DSL Henrik Lindberg Were selectors changed as well, or just case statements? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4511) Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselves
Title: Message Title Nicholas Fagerlund commented on PUP-4511 Re: Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselves This ticket doesn't describe the significance of the bug. Could someone please update with whether this is an internal-only fix, or whether it affects extension APIs? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2894) Assign multiple variables from an array
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2894 Assign multiple variables from an array Change By: Nicholas Fagerlund Summary: lvaluecommaasignmentshouldsplat* Assignmultiplevariablesfrom anarray Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4443) Assign multiple variables from a hash
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4443 Assign multiple variables from a hash Change By: Nicholas Fagerlund Summary: splat-assign Assign multiplevariablesfromahash Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4398) Splat unfolding not supported in method call syntax
Title: Message Title Nicholas Fagerlund commented on PUP-4398 Re: Splat unfolding not supported in method call syntax Docs needs more info on this ticket. Do we consider this a good, practical usage, or a fringe thing that just happens to work? The issue is cloudy because: I'm pretty sure the spec said chain-style calls come after the first argument, followed by additional arguments. This uses multiple arguments as the first argument. It looks like something like (1, 2, 3).with ... should be equivalent to the above usages, but it's not allowed. Having the splat version be special is inconsistent and hard to explain. If you put parentheses around the first argument of a chain-style call, and you just happen to have multiple chain-style calls in a row, they'll eat each others incidental return values. Like this: (*[1, 2, 3]).notice (*[4, 5, 6]).notice (*[4, 5, 6]).notice Notice: Scope(Class[main]): 1 2 3 4 5 6 Notice: Scope(Class[main]): 1 2 3 4 5 6 4 5 6 Notice: Scope(Class[main]): 1 2 3
Jira (PUP-2080) Support functions written in pp
Title: Message Title Nicholas Fagerlund commented on PUP-2080 Re: Support functions written in pp Henrik Lindberg Is the specification at up-to-date with the actual, final implementation? I'm seeing text like, NOTE We may have to wait with supporting calling callables until we have fixed scope since it is not safe to return a lambda and use it later due to the scope implementation in 3x. There is no (non expensive) way of asserting that a function does not leak a Callable. ...which seems to indicate that the spec was never finalized. Or is that still accurate? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Nicholas Fagerlund commented on PUP-2080 Re: Support functions written in pp In order to document this feature, we are going to need some practical, complete, non-trivial examples of .pp functions. Do these exist anywhere? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4277) Case and Selector match should be deep
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-4277
Case and Selector match should be deep
Change By:
Nicholas Fagerlund
Caseandselectormatchshouldberecursive.Currently,thematchoperatoronlyperformsasurfacelevelmatch.{code}case[green,2,$whatever]{[/ee/,Integer[0,10],default]:{notice'yes'}default:{notice'no'}}{code}Theaboveexampleshouldnotice'yes',itcurrentlynotices'no'.UPDATE---Recursivematchingmeansthatthesamematchingrules(asforthesurfacelevel)nowappliesrecursively:*Aliteral{{default}}acceptsanyvalue(e.g.[1,2,3]ismatchedby[1,default,3])*AregexpcanmatchaStringvalue(e.g.helloworldismatchedby/hello.*/)*A value datatype canmatcha data valueofthat type(e.g.3matchesInteger[1,10])*Arraysmustmatchinsizetomatchtheoption*Hashesmatchifthekeysintheoptionhaveanequalkeyinthetestedvalue,andtheoptionkey'svaluematchthetestedvalue.*Arrayentriesandhashentries(values)areprocessedrecursively.Therelevantsectioninthespecificationis:https://github.com/puppetlabs/puppet-specifications/blob/4.0.0/language/expressions.md#case-_expression_(notethereferencetothetag4.0.0asthereareadditionalfeaturesinthe4.1.0version-notablyPUP-4193-lambdasupport).riskassessment:medium(manualvalidatefornow)probability:lowseverity:medium(workarounds)testlayer:unit
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title Nicholas Fagerlund commented on PUP-4193 Re: Add pattern matching to the Puppet DSL Eric Sorenson That ticket was originally about PUP-4277 , but I'll expand it to cover this as well. TBH I'm having a hard time wrapping my head around the original request, but... if I understand this ticket right, it's just that you can use a lambda as a case ...if the control _expression_ is an array, you should have multiple parameters and it will be like the lambda got called with splatting that array?? I'm not sure what happens if the control exp isn't an array. If the lambda's final _expression_ is truthy, that case will match. ..right? I, too, could really use some practical examples. The foo foo alice bob stuff doesn't have a lot of explanatory value. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-2630
Server-set global variables like $::environment get overwritten by client facts
Change By:
Nicholas Fagerlund
REPORTEDPROBLEM---Asperthedocs(http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master)thepuppetmastersetstheglobal$::environmentvariabletocontainthenameofthenode'senvironment.However,ifanodeprovidesafactwiththename'environment'thatfact'svalueoverridestheserver-setenvironment.Thesamehappenswithotherserver-setglobalvariables,like$::servernameand$::serverip.Asaresult,modulescan'treliablyusethesevariablesforwhatevertheirintendedpurposeis.Ifthisistheintendedbehavior,thenthedocsshouldclarifythisanddiscourageuseoftheserver-setvariables,becauseamisbehavingnodecanoverridethem.SOLUTION--- TODO(awaitingupdate) AfterdiscussionwithEricSoerenson,wedecidedthatitwasbesttomakethisanopt-inandthatwearenotaddingafunction-thisforthesakeofconsistencybetween$facts,$trusted_facts,and$server_facts.Thismeans: Atthesameplacewherewecurrentlyset$trusted_factsweshouldalsoset$server_factsifusershaveoptedinThevaluessetin$server_factsarethe@server_factssetinthenodebythecompilerindirection+thecurrentenvironmentnameTheuseroptsinbyusingthesetting:trusted_server_factsThesettingisfalsebydefaultWeissueawarningifanynodeparameterisoverwrittenWeneedatickettoaddadeprecationfortheopt-inbeingsettofalseWeneedaticketfor5.0.0toremovetheoptinandmake$server_factsdefault,andtostopmergingtheserver_factsintothenode'sparameters h3.anexample$server_factshash{serverversion=4.0.0,servername=v85ix8blah.delivery.puppetlabs.net,serverip=10.32.115.182,environment=production}QA---risk:highprobability:mediumseverity:high(hardtodebug,somewhatofasecurityissue,canspoofenvironment)testlayer:acceptance
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-2630
Server-set global variables like $::environment get overwritten by client facts
Change By:
Nicholas Fagerlund
REPORTEDPROBLEM---Asperthedocs(http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master)thepuppetmastersetstheglobal$::environmentvariabletocontainthenameofthenode'senvironment.However,ifanodeprovidesafactwiththename'environment'thatfact'svalueoverridestheserver-setenvironment.Thesamehappenswithotherserver-setglobalvariables,like$::servernameand$::serverip.Asaresult,modulescan'treliablyusethesevariablesforwhatevertheirintendedpurposeis.Ifthisistheintendedbehavior,thenthedocsshouldclarifythisanddiscourageuseoftheserver-setvariables,becauseamisbehavingnodecanoverridethem.SOLUTION--- Addafunctionthatreturnstheserverfacts TODO ( e.g.{{server_facts( awaitingupdate ) }}sincethatmakesitpossibleformoduleauthorstodependonpuppet4.1.0andgetexpectedvalueswithoutanyopt-in.Thisispreferredoversettingyetanotherglobalvariablename. *Separatethelogicinnode(seecommentfromAndyParkerbelowwiththedetails)tomakeitpossibletoretrievetheserversidefactslater*Addafunction{{server_facts()}}thatreturnsahashoftheserversidefacts(thatweresetasideinthenode)*Iftherearenoserversidefacts(puppetapplycase),anemptyhashisreturned*Issueawarningwhenafactoverwritesaserversidefact(butperformtheoverwritesincenotdoingsobreaksAPI)*Decideonrealresolutionofthisissue:(Ping[~eric.sorenson]i.e.possiblydeprecatesettingserverfactsasvariablesintopscope?(Adddeprecationticket,addremovalticketforPUP5.0.0)*ForDOCS,shouldmentionthat{{server_facts()}}shouldbeusedinsteadofusingtopscopevariablesastheycannotbereliedupon. h3.anexample$server_factshash{serverversion=4.0.0,servername=v85ix8blah.delivery.puppetlabs.net,serverip=10.32.115.182,environment=production}QA---risk:highprobability:mediumseverity:high(hardtodebug,somewhatofasecurityissue,canspoofenvironment)testlayer:acceptance
Add Comment
This message was
Jira (PUP-4534) Specify EPP templating language
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4534 Specify EPP templating language Issue Type: Task Assignee: Henrik Lindberg Components: Language Created: 2015/05/06 5:43 PM Priority: Normal Reporter: Nicholas Fagerlund Puppet's EPP templating language lacks a specification. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-966) Backwards incompatible fact type changes
Title: Message Title Nicholas Fagerlund assigned an issue to Unassigned Facter / FACT-966 Backwards incompatible fact type changes Change By: Nicholas Fagerlund Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Issue Type: Task Assignee: Unassigned Components: Language Created: 2015/05/01 11:06 AM Labels: specification Priority: Normal Reporter: Nicholas Fagerlund The section on the access operator alludes to its use on resource references, but there isn't a peer subsection on resource references to go along with the array/string/hash sections. This file in evil made manifest shows most of the tricky bits that the spec doesn't cover. There may also be subtleties I don't know about yet. Add Comment
Jira (PUP-4508) systemd provider should support manual
Title: Message Title Nicholas Fagerlund assigned an issue to Unassigned Puppet / PUP-4508 systemd provider should support manual Change By: Nicholas Fagerlund Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4508) systemd provider should support manual
Title: Message Title Nicholas Fagerlund commented on PUP-4508 Re: systemd provider should support manual I am the wrong assignee for this; it's a product / engineering question. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4465) Document PUP-4201 JSON logging via --logdest
Title: Message Title Nicholas Fagerlund commented on PUP-4465 Re: Document PUP-4201 JSON logging via --logdest Sweet, looks good. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Nicholas Fagerlund commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled Docs impact: for affected versions, remove the known issue note in the future parser page about heredocs. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4465) Document PUP-4201 JSON logging via --logdest
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4465 Document PUP-4201 JSON logging via --logdest Issue Type: Bug Affects Versions: PUP 3.8.0 Assignee: Thomas Hallgren Components: DOCS Created: 2015/04/27 12:58 PM Fix Versions: PUP 3.8.0 Priority: Normal Reporter: Nicholas Fagerlund PUP-4201 added support for specifying --logdest /var/log/somefile.json and getting a (partial) JSON array of log message objects. This wasn't documented. Docs for --logdest are in several files in lib/puppet/application/NAME.rb. The most important ones are apply, agent, and master. All three of these, at least, need edits to reflect the new feature. This feature is quiet enough and odd enough that I believe updating the description of --logdest is the only documentation we need.
Jira (PUP-4437) Update the puppet-agent Repo for 4.0.1 to Incorporate Fix for PUP-4390
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4437 Update the puppet-agent Repo for 4.0.1 to Incorporate Fix for PUP-4390 Change By: Nicholas Fagerlund Fix Version/s: PUP3.8.0 Fix Version/s: PUP4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3863) hiera('some::key', undef) returns empty string
Title: Message Title
Nicholas Fagerlund commented on PUP-3863
Re: hiera('some::key', undef) returns empty string
Henrik Lindberg Ok, will do.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Backslash before $ handled wrongly in heredoc with no escapes enabled
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-4462
Backslash before $ handled wrongly in heredoc with no escapes enabled
Change By:
Nicholas Fagerlund
Ran:{code} $thing=hithere notice(@(ENDINTERP))Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:${thing}Variableenjambed:hey${thing}Variablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\${thing}ENDINTERP{code}Thesinglebackslashbeforethe$causesaproblem.I'mprettysurethisisagainst[thespecificationofheredocs|https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md].Actualresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\hithere{code}Expectedresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\hithereVariablewithdoublebackslashenjambed:\\hithere{code}3.7.5and4.0.0behaveidentically.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-4462) Backslash before $ handled wrongly in heredoc with no escapes enabled
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4462 Backslash before $ handled wrongly in heredoc with no escapes enabled Issue Type: Bug Affects Versions: PUP 4.0.0, PUP 3.7.5 Assignee: Henrik Lindberg Components: Language Created: 2015/04/24 3:40 PM Priority: Normal Reporter: Nicholas Fagerlund Ran: notice(@(END INTERP)) This string should be able to interpolate variables, and all backslashes should
Jira (PUP-4462) Single backslash makes $ disappear in heredoc with no escapes enabled
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4462 Single backslash makes $ disappear in heredoc with no escapes enabled Change By: Nicholas Fagerlund Summary: Backslashbefore Singlebackslashmakes $ handledwrongly disappear inheredocwithnoescapesenabled Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Nicholas Fagerlund Summary: Singlebackslash makes before $ disappear blocksinterpolation inheredocwithnoescapesenabled Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4435) Deprecate Puppet WEBrick and Rack servers
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4435 Deprecate Puppet WEBrick and Rack servers Change By: Nicholas Fagerlund Release Notes: KnownIssue Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4428) The 'err' logging function cannot be called as a statement
Title: Message Title Nicholas Fagerlund commented on PUP-4428 Re: The 'err' logging function cannot be called as a statement This sounds legit to me. I'd forgotten those other log levels even existed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4417) Either affirm or revert changes to allowed environment names
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4417 Either affirm or revert changes to allowed environment names Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Unassigned Created: 2015/04/15 12:02 PM Priority: Normal Reporter: Nicholas Fagerlund According to Henrik Lindberg in PUP-4413, allowed environment names changed in Puppet 4.0.0 as an unintended side-effect of PUP-3268 . The previously forbidden environment names of main, master, agent, and user are now allowed. This change wasn't mentioned in that ticket or in pre-docs. I have not yet independently verified this change. I think we're all against accidental user-facing changes. We should either: Revert them and re-forbid the forbidden names. Affirm the changed behavior. Affirming would mean doing all of the following: Create an acceptance test that proves all four forbidden environment names are now allowed, and prevents them from reverting in the future
Jira (PUP-4413) Add acceptance test that 3.x forbidden env names work in 4.x
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4413 Add acceptance test that 3.x forbidden env names work in 4.x Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4413) Add acceptance test that 3.x forbidden env names work in 4.x
Title: Message Title Nicholas Fagerlund commented on PUP-4413 Re: Add acceptance test that 3.x forbidden env names work in 4.x Henrik Lindberg I created PUP-4417 before you repurposed this. It includes two additional pieces of work that I consider necessary to affirm this behavior change. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4385 Can't write WOMANS HAT emoji with \u unicode escapes Issue Type: Bug Affects Versions: PUP 3.7.5 Assignee: Unassigned Components: Language Created: 2015/04/07 2:41 PM Priority: Minor Reporter: Nicholas Fagerlund Unicode includes a bunch of 5+ hex digit characters now; most notably emoji, but I think there might be some real human language characters in there too. Puppet's \u escape sequences don't accommodate these. The 5-digit versions get truncated, and the alternate 2x4-digit forms result in an error. notice(5 digit unicode \u1f452 hat) # prints: 5 digit unicode ὅ2 hat
Jira (PUP-4378) Resource collectors can be assigned to variables by abusing chaining statements
Title: Message Title Nicholas Fagerlund commented on PUP-4378 Re: Resource collectors can be assigned to variables by abusing chaining statements Henrik Lindberg Seems fine to me. Would this also entail allowing collectors to be used in contexts that require a value? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4378) Resource collectors can be assigned to variables by abusing chaining statements
Title: Message Title
Nicholas Fagerlund created an issue
Puppet / PUP-4378
Resource collectors can be assigned to variables by abusing chaining statements
Issue Type:
Bug
Affects Versions:
PUP 3.7.5
Assignee:
Unassigned
Components:
Language
Created:
2015/04/06 3:53 PM
Priority:
Minor
Reporter:
Nicholas Fagerlund
The 4x parser generally refuses to produce values from resource collectors, and errors if you put one where a value is expected. But since the value of a chaining statement is just the final term of the statement (regardless of arrow direction) and they accept collectors as operands:
notify {I go last.:}
$myweirdchain = (file {/tmp/thing: ensure = file,} -
Jira (PUP-4378) Resource collectors can be assigned to variables by abusing chaining statements
Title: Message Title
Nicholas Fagerlund commented on PUP-4378
Re: Resource collectors can be assigned to variables by abusing chaining statements
Also I have a function that goes like this:
Puppet::Parser::Functions::newfunction(:spew, :doc = Dump an inspect of whatever we get., :type = :rvalue) do |args|
#return args.inspect
return #{args.inspect}\n#{args.collect {|thing| thing.class}.inspect}
end
and if you feed $myweirdchain to THAT, it dumps basically the entire program state, afaict.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4372) Add value of resource expressions to the language spec
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4372 Add value of resource expressions to the language spec Issue Type: Task Assignee: Henrik Lindberg Components: Language Created: 2015/04/03 11:47 AM Priority: Normal Reporter: Nicholas Fagerlund The value of a resource _expression_ is an array of references to all the resources declared by that resource _expression_, in the order in which they were listed. AFAICT, this isn't anywhere in the spec, but it definitely should be. Add Comment
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title
Nicholas Fagerlund created an issue
Puppet / PUP-4374
Splatting attributes into an amended attribute block isn't supported
Issue Type:
Bug
Affects Versions:
PUP 4.0.0, PUP 3.8.0
Assignee:
Unassigned
Components:
Language
Created:
2015/04/03 2:19 PM
Priority:
Normal
Reporter:
Nicholas Fagerlund
Per Henrik Lindberg in email, this is supposed to work... but it totally doesn't.
notify {'first':}
Jira (FACT-903) Allow Facter to query all Facts for non-Admin Windows user
Title: Message Title Nicholas Fagerlund assigned an issue to Michael Smith Facter / FACT-903 Allow Facter to query all Facts for non-Admin Windows user Change By: Nicholas Fagerlund Assignee: NicholasFagerlund MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-869) Amend paths spec to include /opt/puppetlabs/facter/facts.d
Title: Message Title Nicholas Fagerlund commented on FACT-869 Re: Amend paths spec to include /opt/puppetlabs/facter/facts.d So the resolution is that: putting external facts in /etc/ANYTHING is a legacy behavior. it'll probably go away someday... although it's gonna be a minute. if you want to adhere to the spec, the opt directory (and the equivalent ~/.puppetlabs/opt dir) is the one correct place. Right? Okay, cool. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-96) Deprecate 'facter --puppet'
Title: Message Title Nicholas Fagerlund commented on FACT-96 Re: Deprecate 'facter --puppet' Kylo Ginsberg ...no, I don't think so. Come to think of it, I don't think we document the command line tool at all on the website. (!?!?!!?) But! If you run facter --help on the cli, you'll get help text. And that help text lists the --puppet option WITHOUT any mention of its deprecation. That documentation lives in lib/facter/application.rb. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4189) Add all per-user directories to file_paths specification
Title: Message Title Nicholas Fagerlund commented on PUP-4189 Re: Add all per-user directories to file_paths specification I think some of the relevant concerns that led here were: Nick: Consistency in CONTENT of each directory is even more important than consistency in naming. Very opposed to having confdir sometimes contain codedir or vardir; it should always contain the exact same stuff. Josh: Very opposed to weird one-offs like puppet_cache; wants a systematic approach where, if we add a new directory, there are obvious rules showing us exactly where to put it. John: Logical consistency in the mapping of nonroot dirs to root ones is ultimately much more convenient than superficial conveniences like a shallower directory tree. Against giving special treatment to things that would be in etc/ and raising them to the top level of the hierarchy. ...did I remember everyone's concerns right? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4189) Add all per-user directories to file_paths specification
Title: Message Title Nicholas Fagerlund commented on PUP-4189 Re: Add all per-user directories to file_paths specification Here's the proposal Kylo and I just hammered out, on the principle of as above, so below: confdir ~/.puppetlabs/puppet codedir ~/.puppetlabs/code (currently is at $confdir/code, which we decided was wrong for global config... which implies it's wrong for per-user config.) mcollective ~/.puppetlabs/mcollective vardir ~/.puppetlabs/puppet_cache This is different from global, just because there's nothing else quite like it.
Jira (FACT-869) Amend paths spec to include /etc/puppetlabs/facter/facts.d
Title: Message Title Nicholas Fagerlund commented on FACT-869 Re: Amend paths spec to include /etc/puppetlabs/facter/facts.d Kylo just checked it, and we did change the behavior. The relevant facter docs page needs an update as well, then. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-869) Amend paths spec to include /etc/puppetlabs/facter/facts.d
Title: Message Title Nicholas Fagerlund created an issue Facter / FACT-869 Amend paths spec to include /etc/puppetlabs/facter/facts.d Issue Type: Bug Assignee: Eric Sorenson Created: 2015/03/25 12:35 PM Labels: AIO Priority: Normal Reporter: Nicholas Fagerlund According to the docs, facter will load external facts from /etc/facter/facts.d (now under /etc/puppetlabs... I think), but we don't create the dir by default. http://docs.puppetlabs.com/facter/2.4/custom_facts.html#fact-locations If facter still uses that dir, we need to update the spec. Note the parallel to the windows facts.d, which we DO mention in the spec, which is under c:\programdata\facter\facts.d. Add Comment
Jira (FACT-869) Amend paths spec to include /etc/puppetlabs/facter/facts.d
Title: Message Title Nicholas Fagerlund commented on FACT-869 Re: Amend paths spec to include /etc/puppetlabs/facter/facts.d Uh, we also need to investigate to see what the behavior actually is, because we might not have updated it to /etc/puppetlabs/facter/facts.d. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
