Jira (PUP-5885) Files with .. in the path anywhere cannot be used as file sources
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5885 Files with .. in the path anywhere cannot be used as file sources Change By: Kylo Ginsberg Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5865) GPG signing key for the nightlies repo has expired
Title: Message Title Kylo Ginsberg commented on PUP-5865 Re: GPG signing key for the nightlies repo has expired Ping Michael Stahnke. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5865) GPG signing key for the nightlies repo has expired
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5865 GPG signing key for the nightlies repo has expired Change By: Kylo Ginsberg Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5890) Cannot inline metadata for Windows files
Title: Message Title Josh Cooper created an issue Puppet / PUP-5890 Cannot inline metadata for Windows files Issue Type: Bug Assignee: Unassigned Created: 2016/02/11 10:45 PM Fix Versions: PUP 4.4.0 Priority: Normal Reporter: Josh Cooper The compiler terminus cannot inline file metadata for windows files, because it calls Resource#to_ral. That causes the file munge and validation logic to run, and that fails because Windows paths, e.g. c:/foo, are not absolute path on posix. The compiler terminus needs to retrieve file metadata without creating an instance of Puppet::Type::File. Will involve calling Puppet::FileServing::Metadata.indirection directly, and reusing the recurse_remote_metadata logic. Add Comment
Jira (PUP-5890) Cannot inline metadata for Windows files
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5890 Cannot inline metadata for Windows files Change By: Josh Cooper Scope Change Category: Found Scope Change Reason: Assumed static compiler behavior was correct, and must fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Daniel Parks commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Ah, sorry. I realize that my comment was entirely unclear. I meant that it might be possible to modify the error message based on whether or not there was a new line. Of course, that requires knowing where the LPAR that begins the parameters list is, but you must store that information so you can use it in the case of errors. Or maybe you reparse. You would know better than me. It's absolutely a minor edge case, and I don't think it makes sense to "fix" it. There's something very nice about not treating new lines as special. So, a different error message would be very useful in this rare case, and might be quite a bit cheaper. Naturally I don't know if that all balances out. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title
Henrik Lindberg commented on PUP-5849
Re: Newline is not sufficient to avoid parsing as a function call
Where the error occurs you know:
there is a supposed to be a call
the name of the function is an _expression_ - it evaluated to something
it was supposed to be a NAME but it wasn't
It has the AST, and every node in the AST knows the text offset and length of the source text that resulted in every portion of the AST. The source text is also available. The job is to come up with reasonable heuristics to detect the various problems that can lead to the error (it is not a name). It could be a bona fide mistake 1(foo) 'hello'(10) etc. Humans are good at finding problems like this, but a computer is not. You almost need a grammar/parser to figure out the cases. It is like peeping through a very small hole and trying to get the bigger picture.
If we focus on "its on a different line" - then we can detect that (the functions name ends on a different line) than the beginning of the first argument's _expression_ (the '(''s position is unknown, it is somewhere in between), or the ')' position (which is the last position of the entire call) if there are no arguments). Given that, it is possible to use the line index to detect a difference in line number.
i.e. it is doable to produce a better error, but it is not easy. What should it say to make it clear what is going on?
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You
Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Henrik Lindberg commented on PUP-5742 Re: Add ability to create Aliases for Puppet Types in PL The case of what it expects is strange, but the problem with giving a better error for this: expected 'environment::myinteger', actual 'Production::MyInteger' is that a QualifiedReference (i.e. what MyType is), is actually all lower case internally. It is only the initial case that matters, the case of the rest of the name is ignored once it becomes a QualifiedReference. That prevents us from saying expected "Environment::MyType", we could do "Environment::Mytype" at least. There is a utility for producing initial caps for each segment. Ping Thomas Hallgren - can you take a stab at that - file a ticket and fix so it at least gives initial caps if you think that is better. Eric Thompson - any suggestion what would have been more helpful (given we don't know the actual capitalization of the original expected value). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5881) Support "provides" in Metadata.json
Title: Message Title
Julien Pivotto created an issue
Puppet / PUP-5881
Support "provides" in Metadata.json
Issue Type:
Bug
Assignee:
Unassigned
Components:
Modules
Created:
2016/02/11 6:47 AM
Priority:
Normal
Reporter:
Julien Pivotto
The warnings added by the latest versions are intrusive and annoying when you do not use the mentioned modules.
e.g I want to use the mymysql module instead of puppetlabs-mysql.
metadata.json should accept a field "provides", to tell puppet that it supports the same API and functionalities of other modules.
example:
"provides": [
{"name":"puppetlabs-puppetdb","version":"2.0.0"}
Jira (PUP-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title
Henrik Lindberg commented on PUP-5849
Re: Newline is not sufficient to avoid parsing as a function call
First there is lexing, that hacks up the text into tokens, then there is parsing. Parsing builds an Abstract Syntax Tree (AST) under the direction of a grammar. The AST is then validated for semantic errors. Finally the AST is evaluated (that is where calls are made and 1+1 becomes 2). All of that takes place in a Catalog compilation.
In order for something to be a call it must be recognized by the grammar. In this case (simplified):
call: _expression_ LPAR expression_list optional_comma RPAR
In order to NOT recognize LPAR token (i.e. a '(') as signaliing "here are arguments to a call" in this grammar rule, the lexer must deliver another token when it sees a '(' that it lexically can determine as allowed to start a call. Thus when it finds a '(', it must visist preceding characters until it finds a non whitespace, the beginning of the file, or a newline. That can be many characters away from where the '(' is. The lexer must do this for every '(' it sees. That is expensive.
If instead the rule is "cannot be preceded by whitespace for ( to mean list of arguments in a call" then it is enough to look at the immediately preceding character. With this rule it is irritating that you must write a call without a whitespace - e.g.
notice(foo) # a call
# instead of
notice (foo) # not a call
That would break more people as some like to use a space there.
Now that I think about it, we do know about the positions of every newline, and we do know the preceding token; its offset from the beginning of the file, and its
Jira (FACT-1343) Open Source and release the toolchain
Title: Message Title Michael Smith assigned an issue to Michael Stahnke Facter / FACT-1343 Open Source and release the toolchain Change By: Michael Smith Assignee: Michael Stahnke Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5118) Handle duplicate resources when inlining file metadata
Title: Message Title Josh Cooper commented on PUP-5118 Re: Handle duplicate resources when inlining file metadata Also wanted to note that this behavior is currently implemented on the agent where it prevents eval_generated resources from duplicating explicitly managed files. Andy mentions one tricky point in 7ed9025f. If you recurse on /path/to/dir, which generates a /path/to/dir/sub and that attempts to generate /path/to/dir/sub/file, but that resource is already managed, then we don't want to add a duplicate resource for /path/to/dir/sub/file, but we do want to add an edge from the explicit file to the generated parent /path/to/dir/sub. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1343) Open Source and release the toolchain
Title: Message Title Matthew Gyurgyik commented on FACT-1343 Re: Open Source and release the toolchain This would be incredibly helpful for my quest of rebuilding puppet-agent. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5885) Files with .. in the path anywhere cannot be used as file sources
Title: Message Title
Matthaus Owens created an issue
Puppet / PUP-5885
Files with .. in the path anywhere cannot be used as file sources
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/02/11 11:05 AM
Priority:
Normal
Reporter:
Matthaus Owens
The following resource does not work in puppet currently:
file {"/tmp/foo":
ensure => present,
source => 'puppet:///modules/foo..d/bar.txt',
}
Jira (HI-377) Hiera CLI and hiera_hash in Puppet DSL provide different results
Title: Message Title Ben Langfeld commented on HI-377 Re: Hiera CLI and hiera_hash in Puppet DSL provide different results Rob Nelson Did you ever get a resolution to this? I just opened a PE ticket for precisely the same problem with 2015.2.3. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1985) Allow function & class & define parameters to reference earlier parameters
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1985 Allow function & class & define parameters to reference earlier parameters Change By: Eric Thompson QA Highest Test Level: Unit Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1985) Allow function & class & define parameters to reference earlier parameters
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1985 Allow function & class & define parameters to reference earlier parameters Change By: Eric Thompson QA Risk Assessment: Medium High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1985) Allow function & class & define parameters to reference earlier parameters
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1985 Allow function & class & define parameters to reference earlier parameters Change By: Eric Thompson QA Risk Assessment Reason: been like this for a while.. semi-rare use case regression, reported by community Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2339) POST queries to PuppetDB
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2339 POST queries to PuppetDB Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: CLI fixes before release Sprint: PuppetDB 2016- 03 02 - 09 24 Fix Version/s: PDB CLI 0.2.0 Fix Version/s: PDB CLI 0.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this
Jira (PUP-1985) Allow function & class & define parameters to reference earlier parameters
Title: Message Title
Eric Thompson commented on PUP-1985
Re: Allow function & class & define parameters to reference earlier parameters
validated on ubuntu1404 at master SHA: 1c875539df1eb059f2e2aa338c2950126d36bf48
[root@ilmppi47bc4pk4c manifests]# cat site.pp
define foo (
$concurrent_reads = 20,
$concurrent_writes = $concurrent_reads/2,
) { notify{ "$concurrent_writes":} }
foo {'test':}
foo {'test2': concurrent_reads => 10}
root@bcsfyyj29kbophv:~# puppet agent -t --server ilmppi47bc4pk4c.delivery.puppetlabs.net
Info: Using configured environment 'production'
Jira (PUP-4361) 4.x Language - Puppet 4 Language fixes and enhancements
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4361 4.x Language - Puppet 4 Language fixes and enhancements Change By: Henrik Lindberg Summary: 4.x Language - Puppet 4 Language fixes / and enhancements Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4361) Puppet 4 Language fixes/enhancements
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4361 Puppet 4 Language fixes/enhancements Change By: Henrik Lindberg Epic Name: Language 4 Fixes .x Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2426) (MAINT) Pretty query results by default
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2426 (MAINT) Pretty query results by default Issue Type: Bug Assignee: Unassigned Created: 2016/02/11 12:18 PM Priority: Normal Reporter: gepetto-bot Users can disable pretty printing by passing --pretty false Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5887) Interpolation in interpolation nested string does not work.
Title: Message Title Henrik Lindberg commented on PUP-5887 Re: Interpolation in interpolation nested string does not work. Ping on NPUP-18 when there are test cases (in case there are more things that should be tested than the simple example here. i.e. 3 levels, several in a row...) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5887) Interpolation in interpolation nested string does not work.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5887 Interpolation in interpolation nested string does not work. Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2426) (MAINT) Pretty query results by default
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2426 (MAINT) Pretty query results by default Change By: gepetto-bot Sprint: PuppetDB 2016-02-24 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5887) Interpolation in interpolation nested string does not work.
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-5887
Interpolation in interpolation nested string does not work.
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/02/11 12:20 PM
Fix Versions:
PUP 4.4.0
Priority:
Normal
Reporter:
Henrik Lindberg
If you do this:
notice "${"${foo}"}"
There is a syntax error at the closing "
If doing this (i.e. no interpolation in inner string):
notice "${ "\$foo" }"
Jira (PUP-5712) TypeParser cannot handle negative numbers
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5712 TypeParser cannot handle negative numbers Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5742 Add ability to create Aliases for Puppet Types in PL Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Christopher Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server I created an epic for this and will probably break this down into multiple tickets when we get closer to working on it. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1985) Allow function & class & define parameters to reference earlier parameters
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1985 Allow function & class & define parameters to reference earlier parameters Change By: Eric Thompson QA Risk Assessment: High Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1985) Allow function & class & define parameters to reference earlier parameters
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1985 Allow function & class & define parameters to reference earlier parameters Change By: Eric Thompson QA Risk Assessment Reason: High impact on user been like this for a while.. semi-rare use case Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5886) Theme: Language
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5886 Theme: Language Issue Type: Epic Assignee: Unassigned Created: 2016/02/11 12:14 PM Priority: Normal Reporter: Henrik Lindberg THIS IS A CROSS TEAM EPIC - DO NOT PUT IN A SPRINT This thematic epic is for Language fixes and enhancements over all versions. Version specific epics should be created - e.g. "4.x Language", "5.x Language" Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-1526) Package type should support environment variables
Title: Message Title Johan Lyheden commented on PUP-1526 Re: Package type should support environment variables +1 We have a poorly packaged 3rd party RPM that does conditional logic based on variables set in the environment. It would be great if we could set these in the package type instead of resorting to hacky exec. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5805) Parser never sets location on RHS of "resource without title" expressions
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-5805 Parser never sets location on RHS of "resource without title" expressions Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5861) Puppet Array & Hash types should present themselves as just Array/Hash when they are default
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5861 Puppet Array & Hash types should present themselves as just Array/Hash when they are default Change By: Thomas Hallgren Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5880) Support optional dependencies in Metadata.json
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5880
Support optional dependencies in Metadata.json
Change By:
Julien Pivotto
I am trying the latest agent release and warnings have been added when modules dependencies are missing.However that message is not relevant because I do not use the features of those so-called dependencies.{code}├─┬ puppetlabs-puppetdb (v5.0.0)│ ├── UNMET DEPENDENCY puppetlabs-postgresql (>= 4.0.0 <5.0.0)│ ├── UNMET DEPENDENCY puppetlabs-firewall (>= 1.1.3 <2.0.0){code}{code}├─┬ spotify-puppetexplorer (v1.0.1)│ ├── UNMET DEPENDENCY puppetlabs-apt (>= 1.0.0)│ └─┬ puppetlabs-apache (v1.8.0)│ ├── puppetlabs-stdlib (v4.11.0)│ └── puppetlabs-concat (v2.1.0){code}I do not use pgsql or the firewall and I only have CentOS machines.We should be able to make a difference between optional and mandatory puppetmodules in metadata.json. Wanted behaviour:Optional dependency is missing: do nothingOptional dependency is present: do nothingOptional dependency is present but its version conflicts with the one from metadata.json: warn the user
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5805) Parser never sets location on RHS of "resource without title" expressions
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5805 Parser never sets location on RHS of "resource without title" expressions Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5805) Parser never sets location on RHS of "resource without title" expressions
Title: Message Title Thomas Hallgren commented on PUP-5805 Re: Parser never sets location on RHS of "resource without title" expressions Merged to master at 9becff8 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5880) Support optional dependencies in Metadata.json
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5880
Support optional dependencies in Metadata.json
Change By:
Julien Pivotto
I am trying the latest agent release and warnings have been added when modules dependencies are missing.However that message is not relevant because I do not use the features of those so-called dependencies.{code}├─┬ puppetlabs-puppetdb (v5.0.0)│ ├── UNMET DEPENDENCY puppetlabs-postgresql (>= 4.0.0 <5.0.0)│ ├── UNMET DEPENDENCY puppetlabs-firewall (>= 1.1.3 <2.0.0){code}{code}├─┬ spotify-puppetexplorer (v1.0.1)│ ├── UNMET DEPENDENCY puppetlabs-apt (>= 1.0.0)│ └─┬ puppetlabs-apache (v1.8.0)│ ├── puppetlabs-stdlib (v4.11.0)│ └── puppetlabs-concat (v2.1.0){code}I do not use pgsql or the firewall and I only have CentOS machines.We should be able to make a difference between optional and mandatory puppetmodules in metadata.json.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5880) Support optional dependencies in Metadata.json
Title: Message Title Julien Pivotto created an issue Puppet / PUP-5880 Support optional dependencies in Metadata.json Issue Type: Bug Assignee: Unassigned Components: Modules Created: 2016/02/11 6:25 AM Priority: Normal Reporter: Julien Pivotto Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you
Jira (PUP-5861) Puppet Array & Hash types should present themselves as just Array/Hash when they are default
Title: Message Title Thomas Hallgren commented on PUP-5861 Re: Puppet Array & Hash types should present themselves as just Array/Hash when they are default Merged to master at 437310a Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5861) Puppet Array & Hash types should present themselves as just Array/Hash when they are default
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-5861 Puppet Array & Hash types should present themselves as just Array/Hash when they are default Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2018) `puppet certificate generate` Generates Two CSRs in One Run
Title: Message Title Rachel Kelly updated an issue Puppet / PUP-2018 `puppet certificate generate` Generates Two CSRs in One Run Change By: Rachel Kelly CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1342) Update Facter Acceptance tests for cisco-7
Title: Message Title Stan Duffy commented on FACT-1342 Re: Update Facter Acceptance tests for cisco-7 Now that Beaker 2.34.0 is out, this is ready to be merged. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2424) DELETE FROM edges is extremely slow
Title: Message Title Daniele Sluijters created an issue PuppetDB / PDB-2424 DELETE FROM edges is extremely slow Issue Type: Bug Assignee: Unassigned Created: 2016/02/11 8:00 AM Priority: Normal Reporter: Daniele Sluijters We were seeing a lot of DELETE FROM edges queries taking 4-6s or more. We added some indices on edges which seems to have solved it: "edges_certname_idx" btree (certname) "edges_source_hex_idx" btree (encode(source, 'hex'::text)) "edges_target_hex_idx" btree (encode(target, 'hex'::text)) "edges_type_idx" btree (type)
Jira (PUP-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Henrik Lindberg THIS IS A CROSS TEAM EPIC - DO NOT PUT IN A SPRINT. EACH TEAM NEEDS SEPARATE EPIC SUPPORTING THIS. Sensitive information such as passwords or key files contained within Puppet catalogs leaks into locations such as PuppetDB or syslog. This elevates the necessary security that must be enforced on these external systems.It would be valuable to give manifest/module authors the ability to specify resource properties (such as attributes or titles) which are sensitive. Components downstream from the catalog compiler could then choose how to handle sensitive data. For example, the master could redact such fields from the catalog before sending it to PuppetDB. The agent could be configured to obscure sensitive resource titles from the log when they are acted upon.One possible way to do this would be the addition of a "sensitive" resource type that is compiled into the catalog. Each instance would specific resource fields to be selected and the preferred means of redaction. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-5705) As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes
Title: Message Title Kurt Wall assigned an issue to qa-team Puppet / PUP-5705 As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes Change By: Kurt Wall Assignee: Kurt Wall qa-team Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1340) Update Facter Acceptance tests for cisco-5
Title: Message Title Stan Duffy commented on FACT-1340 Re: Update Facter Acceptance tests for cisco-5 Now that Beaker 2.34.0 is out, this is ready to be merged. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5878) acceptance: agent can reconnect after master failure
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-5878 acceptance: agent can reconnect after master failure Change By: John Duarte Assignee: qa-team Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5824) Interpolation of an empty variable %{} or %{::} should yield an empty string
Title: Message Title
Sean Griffin assigned an issue to Sean Griffin
Puppet / PUP-5824
Interpolation of an empty variable %{} or %{::} should yield an empty string
Change By:
Sean Griffin
Assignee:
qa Sean Griffin
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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 (HI-494) Interpolation of the empty variable %{} has changed
Title: Message Title
Sean Griffin assigned an issue to Sean Griffin
Hiera / HI-494
Interpolation of the empty variable %{} has changed
Change By:
Sean Griffin
Assignee:
qa Sean Griffin
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2425) Excessive long running select count query
Title: Message Title Daniele Sluijters created an issue PuppetDB / PDB-2425 Excessive long running select count query Issue Type: Bug Assignee: Unassigned Created: 2016/02/11 8:02 AM Priority: Normal Reporter: Daniele Sluijters We're seeing a lot of excessively long running select queries 00:00:41.200229 | SELECT count(*) AS c FROM catalogs, catalog_resources, certnames WHERE ((catalogs.id = catalog_resources.catalog_id AND cer tnames.certname = catalogs.certname) AND (certnames.deactivated IS NULL AND certnames.expired IS NULL)) 00:00:37.913217 | SELECT count(*) AS c FROM catalogs, catalog_resources, certnames WHERE ((catalogs.id = catalog_resources.catalog_id AND cer tnames.certname = catalogs.certname) AND
Jira (PUP-5861) Puppet Array & Hash types should present themselves as just Array/Hash when they are default
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5861 Puppet Array & Hash types should present themselves as just Array/Hash when they are default Change By: Thomas Hallgren Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5837) reverse_each and step functions should return undef when given a block to avoid confusion
Title: Message Title Henrik Lindberg commented on PUP-5837 Re: reverse_each and step functions should return undef when given a block to avoid confusion merged to master at: 9ddb4a8 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Henrik Lindberg commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Whitespace (and thus newlines) are not significant in puppet except for the [] operator where it must be preceded by whitespace (or start of file) to be recognized as the start of a literal array. That is what the specification says, so this is not a "bug" in the sense that it does not comply with the spec. As you figured out, the ; operator helps remove ambiguities. The one you found is not the only one in the language - you have the same problem if following a bare word with a literal hash. What we could perhaps do is to require that for a call with parameters to be recognized there can be no space between the function's name, and the left parenthesis, such that: foo(1)# wors foo (1) # is the word 'foo' followed by 1 in parentheses that evaluates to 1. error because the 'foo' has no effect To change that would be a breaking change. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5849 Newline is not sufficient to avoid parsing as a function call Change By: Henrik Lindberg Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5824) Interpolation of an empty variable %{} or %{::} should yield an empty string
Title: Message Title
Sean Griffin assigned an issue to Unassigned
Puppet / PUP-5824
Interpolation of an empty variable %{} or %{::} should yield an empty string
Change By:
Sean Griffin
Assignee:
Sean Griffin
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5835) Symbol in scope; puppet apply -e 'notify { $environment: }' raises an exception
Title: Message Title
Sean Griffin assigned an issue to Unassigned
Puppet / PUP-5835
Symbol in scope; puppet apply -e 'notify { $environment: }' raises an exception
Change By:
Sean Griffin
Assignee:
Sean Griffin
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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 (HI-494) Interpolation of the empty variable %{} has changed
Title: Message Title
Sean Griffin assigned an issue to Unassigned
Hiera / HI-494
Interpolation of the empty variable %{} has changed
Change By:
Sean Griffin
Assignee:
Sean Griffin
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5836) Splat operator should turn Iterator into an array
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5836 Splat operator should turn Iterator into an array Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5888) Add new subcommands to `puppet help`
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5888 Add new subcommands to `puppet help` Change By: Kylo Ginsberg Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5888) Add new subcommands to `puppet help`
Title: Message Title Kylo Ginsberg commented on PUP-5888 Re: Add new subcommands to `puppet help` Assigning this to PUP 4.x just as a (weak) reminder to keep it on our radar. Basically, I'd sure love to fix this. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5836) Splat operator should turn Iterator into an array
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5836 Splat operator should turn Iterator into an array Change By: Eric Thompson Assignee: Sean Griffin Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5888) Add new subcommands to `puppet help`
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-5888 Add new subcommands to `puppet help` Change By: Kylo Ginsberg Affects Version/s: PE 2015.3.0 Affects Version/s: PUP 4.3.2 Key: PE PUP - 12699 5888 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1519) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number
Title: Message Title Elizabeth Wittig updated an issue Puppet / PUP-1519 Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number Change By: Elizabeth Wittig CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5836) Splat operator should turn Iterator into an array
Title: Message Title
Eric Thompson commented on PUP-5836
Re: Splat operator should turn Iterator into an array
validated on ubuntu1404 at master SHA: 1c875539df1eb059f2e2aa338c2950126d36bf48
root@bcsfyyj29kbophv:/etc/puppetlabs/code/environments/production# puppet apply -e 'file{"/tmp/splat_out": content => "${*[1,2,3].reverse_each}"}'
Notice: Compiled catalog for bcsfyyj29kbophv.delivery.puppetlabs.net in environment production in 0.04 seconds
Notice: /Stage[main]/Main/File[/tmp/splat_out]/content: content changed '{md5}a11f9ec5c5dd08c944aaff367e1f542d' to '{md5}b97c72702f44c66c2de2ecdfe321705f'
Notice: Applied catalog in 0.05 seconds
root@bcsfyyj29kbophv:/etc/puppetlabs/code/environments/production# cat /tmp/splat_out
[3, 2, 1]root@bcsfyyj29kbophv:/etc/puppetlabs/code/environments/production# puppet apply -e 'notice(*[1,2,3].reverse_each)'
Notice: Scope(Class[main]): 3 2 1
Notice: Compiled catalog for bcsfyyj29kbophv.delivery.puppetlabs.net in environment production in 0.04 seconds
Notice: Applied catalog in 0.02 seconds
Jira (PUP-4818) PUP-121 (relative namespacing) was never fully resolved in 3.x future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never fully resolved in 3.x future parser Change By: Henrik Lindberg Release Notes Summary: One part of the "relative namespacing" feature was not removed when using future parser. When a class was declared with the resource like _expression_ the references to classes where still interpreted as being relative. This is now fixed and should help with migration to 4.x as the 3.x future parser will now also use absolute naming in these cases. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install or upgrades of PE, they're enabled globally with application orchestration or not. * If file-sync is enabled, file metadata will be inlined into the catalog. If file-sync is not enabled, file metadata will not be inlined and catalog compilation will precede as it did prior to static catalogs.* If users opt out of file sync and want to use static catalogs, they'll need to follow the OSS instructions for reaching those endpoints. Note that if both endpoints aren't included, Puppet Server will fail.h2. Turn it offglobal setting (puppet.conf, [main]) or per-environment (environment.conf [main])h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired stateh2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Eric Thompson commented on PUP-5742 Re: Add ability to create Aliases for Puppet Types in PL what happens if you have a module named "environment"? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5114) Retrieve content using content_uri
Title: Message Title Branan Riley assigned an issue to Branan Riley Puppet / PUP-5114 Retrieve content using content_uri Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5742 Add ability to create Aliases for Puppet Types in PL Change By: Eric Thompson QA Risk Severity: Low Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5742 Add ability to create Aliases for Puppet Types in PL Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Probability Reason: new feature, power users only. QA Risk Assessment: High Medium QA Risk Severity Reason: can use native types QA Risk Probability: Low QA Risk Severity: Low QA Highest Test Level Reason: later acceptance tests for the Type system generally Add Comment
Jira (PUP-4818) PUP-121 (relative namespacing) was never fully resolved in 3.x future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never fully resolved in 3.x future parser Change By: Henrik Lindberg Summary: PUP-121 (relative namespacing) was never actually fully resolved in 3.x future parser Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2428) Allow Setting The Interval for Each of The Garbage Collection Queries Individually
Title: Message Title Nick Walker created an issue PuppetDB / PDB-2428 Allow Setting The Interval for Each of The Garbage Collection Queries Individually Issue Type: Improvement Assignee: Unassigned Created: 2016/02/11 3:34 PM Labels: tcse Priority: Normal Reporter: Nick Walker Currently we have gc-interval which can be tuned up and down, however, it runs a few different queries some of which I want to run more often and some I'd like to run very infrequently. I want the run the query to remove reports frequently say every 10 minutes but I don't want all of the other queries to run because in my environment the other queries don't actually delete anything but do take a long time to complete and use up resources. I'd like to be able to specify a frequency to run each of the different GC queries so that I can tune the performance of my puppetdb database based on the specifics of my environment. If I'm using node-purge-ttl and I add and remove nodes a lot I may wish to have that query run more frequently. For other queries that rarely remove any data, I'd like to run them very infrequently maybe once a week or month.
Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Eric Thompson commented on PUP-5742 Re: Add ability to create Aliases for Puppet Types in PL validated on ubuntu at master SHA: 1c875539df1eb059f2e2aa338c2950126d36bf48 root@bcsfyyj29kbophv:/etc/puppetlabs/code/environments/production# cat types/myinteger.pp type Environment::MyInteger = Integer root@bcsfyyj29kbophv:/etc/puppetlabs/code/environments/production# cat modules/mymodule/types/myinteger.pp type MyModule::MyInteger = Integer root@bcsfyyj29kbophv:/etc/puppetlabs/code/environments/production# cat modules/mymodule/types/somewhere/myinteger.pp type MyModule::Somewhere::MyInteger = Integer root@bcsfyyj29kbophv:/etc/puppetlabs/code/environments/production# puppet apply -e 'type MyInteger = Integer; notice 42 =~ MyInteger' Notice: Scope(Class[main]): true Notice: Compiled catalog for bcsfyyj29kbophv.delivery.puppetlabs.net in environment production in 0.04 seconds
Jira (PUP-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Daniel Parks commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Thanks for the response — that totally makes sense. I've run into similar problems in _javascript_. I do really like that newline isn't special cased here. It's actually not so much that this behavior is a problem, as it is that when it bites you it's entirely mystifying. It might be worth finding some way to improve the error message — though I suppose adding more look behind to find a newline only in that case might be difficult. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Daniel Parks commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Oh, of course — the error I run into isn't from the parse. I guess it would still be possible to look for a previous newline, though. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5845) Add the function type()
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5845 Add the function type() Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4818) PUP-121 (relative namespacing) was never fully resolved in 3.x future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never fully resolved in 3.x future parser Change By: Henrik Lindberg Release Notes Summary: THIS NOTE ONLY APPLIES TO 3.8.7 RELEASE. One part of the "relative namespacing" feature was not removed when using future parser. When a class was declared with the resource like _expression_ the references to classes where still interpreted as being relative. This is now fixed and should help with migration to 4.x as the 3.x future parser will now also use absolute naming in these cases. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5824) Interpolation of an empty variable %{} or %{::} should yield an empty string
Title: Message Title
Sean Griffin updated an issue
Puppet / PUP-5824
Interpolation of an empty variable %{} or %{::} should yield an empty string
Change By:
Sean Griffin
Attachment:
pup-5824-manifest
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Eric Thompson commented on PUP-5742 Re: Add ability to create Aliases for Puppet Types in PL ok, this works, but it's kinda surprising to me. particularly the environment case. root@bcsfyyj29kbophv:~# puppet apply -e 'notice 42 =~ Environment::MyInteger' Error: Evaluation Error: Error while evaluating a Type-Name, The code loaded from /etc/puppetlabs/code/environments/production/types/myinteger.pp produced type with the wrong name, expected 'environment::myinteger', actual 'Production::MyInteger' at line 1:14 on node bcsfyyj29kbophv.delivery.puppetlabs.net root@bcsfyyj29kbophv:~# vi /etc/puppetlabs/code/environments/production/types/myinteger.pp root@bcsfyyj29kbophv:~# puppet apply -e 'notice 42 =~ Environment::MyInteger' Notice: Scope(Class[main]): true Notice: Compiled catalog for bcsfyyj29kbophv.delivery.puppetlabs.net in environment production in 0.04 seconds Notice: Applied catalog in 0.02 seconds root@bcsfyyj29kbophv:~# cat /etc/puppetlabs/code/environments/production/types/myinteger.pp type Environment::MyInteger = Integer
Jira (PUP-5835) Symbol in scope; puppet apply -e 'notify { $environment: }' raises an exception
Title: Message Title
Sean Griffin assigned an issue to Sean Griffin
Puppet / PUP-5835
Symbol in scope; puppet apply -e 'notify { $environment: }' raises an exception
Change By:
Sean Griffin
Assignee:
qa Sean Griffin
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg commented on PUP-4818 Re: PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Nicholas Fagerlund Would you say it is the "class as resource" that does it wrong, or was that only used to illustrate and the problem is much wider? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2427) (maint) update install modes to get stable tests green
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2427 (maint) update install modes to get stable tests green Change By: gepetto-bot Sprint: PuppetDB 2016-02-24 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install or upgrades of PE, they're enabled globally with application orchestration or not. * If users opt out of file sync and want to use static catalogs, they'll need to follow the OSS instructions for reaching those endpoints. Note that if both endpoints aren't included, Puppet Server will fail. h2. Turn it offglobal setting (puppet.conf, [main]) or per-environment (environment.conf [main])h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state * (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me) h2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2427) (maint) update install modes to get stable tests green
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2427 (maint) update install modes to get stable tests green Issue Type: Bug Assignee: Unassigned Created: 2016/02/11 2:17 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Henrik Lindberg commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Using newline as the distinction is much more expensive to compute. We throw away all whitespace, and we use "look behind" to see if "preceded by whitespace" in the lexer (a one char look-behind). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg commented on PUP-4818 Re: PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Replacing the resource like instantiations with include makes the examples work. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5845) Add the function type()
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5845
Add the function type()
Change By:
Henrik Lindberg
Add the function {{type\(x , inference_type = detailed )}} that produces the type of the given argument. The puppet data type is produced by the function using an inference algorithm of given inference_type. The default is to use full detailed inference.The quality optional parameter can be one of:* 'generalized' - reduces type and removes length constraints* 'reduced' - reduces types to common types in collections* 'detailed' - retains all inferred types with highest possible qualitySee documentation of the function for details and examples. There is currently a function named {{type_of}} in stdlib. This is the same basic functionality but available in core as it is odd to not have this directly in core. The new function also gives the ability to do inference of a degree of generality This was made possible in the work done on PUP-5742 as the {{type}} keyword was changed from just being reserved for future use.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5845) Add the function type()
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5845
Add the function type()
Change By:
Henrik Lindberg
Add the function {{type\(x, inference_type = detailed)}} that produces the type of the given argument.The puppet data type is produced by the function using an inference algorithm of given inference_type. The default is to use full detailed inference.The quality optional parameter can be one of:* 'generalized' - reduces type and removes length constraints* 'reduced' - reduces types to common types in collections* 'detailed' - retains all inferred types with highest possible qualitySee documentation of the function for details and examples.There is currently a function named {{type_of}} in stdlib. This is the same basic functionality but available in core as it is odd to not have this directly in core. The new function also gives the ability to do inference of a degree of generalityThis was made possible in the work done on PUP-5742 as the {{type}} keyword was changed from just being reserved for future use. USAGEUsers are encouraged to use {{assert_type}} with default error message, but when writing custom error messages the {{type}} function is required in order to describe what was wrong if the value did not match the expected type. i.e. the typical use is:{code:puppet}define example() { $x = some_function() unless arg =~ Integer {fail("Expected some_function() to produce an Integer, but produced a value of type:' ${ type($x) }'" }}{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this
Jira (PUP-5845) Add the function type()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5845 Add the function type() Change By: Henrik Lindberg Release Notes Summary: The function type(x, inference_type = detailed) has been added. It produces the type of the given argument. This function removes the need to use the standard lib function type_of which does the same thing. The function can produce generalized, reduced or detailed type information. This is useful when producing custom error messages when a type check fails. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5844) Add the Object type to the Puppet Type system
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5844 Add the Object type to the Puppet Type system Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-410) 4.0 Language - Complete Implementation of Language based on the EGrammar
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-410 4.0 Language - Complete Implementation of Language based on the EGrammar Change By: Henrik Lindberg Summary: 4.0 Language - Complete Implementation of Language based on the EGrammar Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4750) Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4750 Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead) Change By: Henrik Lindberg Environment: Node:=kernel => AIXkernelmajversion => 7100kernelrelease => 7100-03-04-1441kernelversion => 7100puppetversion => 3.2.3rubysitedir => /opt/freeware/lib/ruby/site_ruby/2.0.0rubyversion => 2.0.0Master1:kernel => Linuxkernelmajversion => 2.6kernelrelease => 2.6.32-431.20.3.el6.x86_64kernelversion => 2.6.32lsbdistcodename => Santiagolsbdistdescription => Red Hat Enterprise Linux Server release 6.5 (Santiago)lsbdistid => RedHatEnterpriseServerlsbdistrelease => 6.5lsbmajdistrelease => 6lsbrelease => :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarchpuppetversion => 3.4.3rubysitedir => /usr/lib/ruby/site_ruby/1.8rubyversion => 1.8.7Master2:kernel => Linuxkernelmajversion => 2.6kernelrelease => 2.6.32-504.16.2.el6.x86_64kernelversion => 2.6.32lsbdistcodename => Santiagolsbdistdescription => Red Hat Enterprise Linux Server release 6.6 (Santiago)lsbdistid => RedHatEnterpriseServerlsbdistrelease => 6.6lsbmajdistrelease => 6lsbminordistrelease => 6lsbrelease => :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarchpuppetversion => 3.8.1rubyplatform => x86_64-linuxrubysitedir => /usr/lib/ruby/site_ruby/1.8rubyversion => 1.8.7 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4750) Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4750 Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead) Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4750) Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead)
Title: Message Title Henrik Lindberg commented on PUP-4750 Re: Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead) I cannot make heads or tails of this issue. Need a reproducible example that does not involve a module from the forge. Alternatively report the issue to the author of the module. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4750) Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead)
Title: Message Title Henrik Lindberg assigned an issue to Ruediger Mueck Puppet / PUP-4750 Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead) Change By: Henrik Lindberg Assignee: Ruediger Mueck Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-477) Implement Strict Numbers
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-477
Implement Strict Numbers
Change By:
Henrik Lindberg
Background---* < 3.x && 3.x without future parser - all values are strings, and numeric operations has a variety of problems* 3x future parser has a hybrid string / number auto type conversion. Early versions of the future parser had paradoxes in handing numeric values that were fixed late in the 3.x series (use 3.8.x with future parser). * 4.x is the same as 3.x future parser The experimental current 4x evaluator also has this, but with currently fixed paradoxes in this handling automatic conversion between string and number . It continues to be a problem balancing between "being helpful" and "being correct and free of paradox".It would be much cleaner to never automatically convert between numbers and strings (except possibly at boundaries; converting numerical facts in string form .This Feature---When {{\--strict}} mode is on, arithmetic on a {{String}} leads to real numbers) a warning or error as dictated by the mode . When strict is 'ignored' auto conversion still takes place. Depends on---This feature depends on PUP-5889, that there is a strict flag, and PUP-484 since it is currently not possible to convert values.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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
