Jira (PUP-6013) The EL6 YUM repository is pointing at EL7 packages
Title: Message Title Trevor Vaughan commented on PUP-6013 Re: The EL6 YUM repository is pointing at EL7 packages Hi All, just wondering if this is going to be fixed? EL6 clients still can't update from this repo. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title
R.I.Pienaar commented on PUP-6091
Re: Lookup CLI should use unquoted dot in key as sub-lookup
Facter cli has {key.key.0.key}
to dig into hashes and arrays. A function that does exact same and return undef when not found would be great for consistency but as you say it's not perfect
Consistently not perfect beats all being different imo
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-25) Implement a 'repl' command.
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-25 Implement a 'repl' command. Change By: Peter Huene Story Points: 2 1 Sprint: Language Triage 2016-04-06 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4683) repair winrm/winrm-fs gem
Title: Message Title Ethan Brown commented on PUP-4683 Re: repair winrm/winrm-fs gem FYI - there is a new winrm v2 branch up at https://github.com/WinRb/WinRM/pull/191 that we should probably keep an eye on. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5879) Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8
Title: Message Title Ethan Brown commented on PUP-5879 Re: Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8 One area for functional review that we didn't get to in PUP-5768 , that seems logical to include as functional review for this ticket (as I believe it depends on this ticket being resolved): With a user that is not Unicode, I would like to see an exec resource execute under a path that contains Unicode characters. This should be possible by: Adding a path to the main section of puppet.conf to include a Unicode path with a well-known binary in it - see https://docs.puppetlabs.com/puppet/latest/reference/configuration.html#path Also add to the current PATH another Unicode path with a well-known binary in it - this should test lib/puppet/defaults.rb changes Using exec to launch the binaries and confirm that the current launching shell PATH and the settings from puppet.conf are used properly when searching Performing these tests should verify that the config file is read correctly as UTF-8 and that ENV is not getting mangled. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-5768) Fix problematic usage of ENV for Windows
Title: Message Title Ethan Brown commented on PUP-5768 Re: Fix problematic usage of ENV for Windows PUP-6035 captures some of the details we're interested in for running as a Unicode user. I will add details there for an alternate test for this particular scenario, given this ticket is closed. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-75) Strings calls 'interpret_any' with the wrong number of arguments
Title: Message Title Henrik Lindberg commented on PDOC-75 Re: Strings calls 'interpret_any' with the wrong number of arguments merged to master: a3227b8 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title
Henrik Lindberg commented on PUP-6091
Re: Lookup CLI should use unquoted dot in key as sub-lookup
In the puppet language I am contemplating that we should support a more comprehensive slice, but it is somewhat muddled by the fact that it can only be supported on arrays.
Currently you have to write a long chain of [key] in puppet, and if you want to protect against an undef somewhere in the chain it gets quite horrible.
$lookup('root')[key1][key2][0][key3]
That would be much more nicely expressed as:
$lookup('root')[key1, key2, 0, key3]
However if the first level returns an Array, that does not work since it slices a range from the Array, so you would have to navigate to the first hash in the drill down before being able to use the "multi key" access.
OTOH, supporting the dot notation "natively" in puppet will not work as the dot means "member call". That is simply not going to work.
One option is to add a function that slices like the dot notation.
lookup(¨root').access(key1, key2, 0, key3)
I think that is the best option; easy to understand and implement.
The other alternative is to support the 'sub-lookup' in lookup everywhere (or worse UX, have an option in the call that allows users to state something like sublookup => true (which then requires quoting if key has verbatim dots). Using exactly the same notation in the lookup key is not nice; working with strings in puppet to construct keys is not fun (say you want to iterate over 0-n
Jira (PUP-6090) Output of iterator type results in unhandled exception
Title: Message Title Henrik Lindberg commented on PUP-6090 Re: Output of iterator type results in unhandled exception Yeah, that is were I got stuck on this when I last thought about making that change (unfold args to params + auto index). Suggest that native impl changes to always use Array representation, and that we consider changing the "auto index" for Puppet 5.0.0. And that we use this ticket to let notice + similar 4x functions do to_a on an Iterator. We could also consider doing a to_a in the transformation to the 3.x function API. IIRC, now we error if it is given an Iterator. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title Thomas Hallgren commented on PUP-6091 Re: Lookup CLI should use unquoted dot in key as sub-lookup Assume that you have a hash that will be found with key 'a'. The hash contains the key 'b'. The 'a' key and it's associated hash with a 'b' key is defined in more places than one and you want to merge the 'b' values found (it's an array or hash). The Hiera CLI will lookup and merge all values found with a 'b' key in an 'a' hash. In other words, Hiera will merge all leafs that it finds. If we implement this in the lookup CLI however, it will receive one merged root 'a' from the underlying data providers and then extract the leaf 'b'. Add negating keys to the equation before assuming that this would be equivalent when doing a deep merge. This is not the only objection though. If we do this for the sake of consistency, what about consistency between the lookup CLI and the lookup Puppet API? There is no support for dotted keys in the API. Isn't that even more confusing? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6090) Output of iterator type results in unhandled exception
Title: Message Title
Peter Huene commented on PUP-6090
Re: Output of iterator type results in unhandled exception
In the native implementation, the constructed iterator knows its input sequence type (currently always the same as the data source given that no iterator type currently transforms the sequence). If map returned a "map iterator" that produces a value by lazily invoking the block, any chained iterator would see the output of that iterator not as a key-value sequence but as a "regular" sequence (i.e. as if you were iterating an array), because that's what map returns. Thus, tacking on an each call to the code above would indeed lazily produce only the key values. This wasn't terribly complex to make work, at least for the native implementation.
Regardless, I'm open to making iterators always represent themselves as arrays; that would be easy to change.
If we can add the ability to automatically unfold single-array arguments to blocks, then that would be excellent, and that would help solve the problem of the inconsistency between the each and reverse_each interfaces; however, that would obviously be a breaking change for something expecting an index like [[foo, baz]].each |$index, $value| {}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Henrik Lindberg commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash I can imagine reserving Unit in the type system so that it is an error to use it in the Puppet Language (rather than it being interpreted as Resource type). If we should report Unit as Any (which is not 100% correct) or invent some other (parseable) notation for emptyness. An obvious choice would be say Array[], but that does not currently parse - I would prefer that over both the current clunky Array[Unit, 0, 0], and Array[Any, 0, 0] as it makes the emptiness explicit. Those are really the only places were it surfaces unless there is some internal error. Later, if/when we get to adding type parameters, the Unit type has probably played out its role and will be replaced by a type parameter that is a specific reference - i.e. if you accept something like Array[] (where is fantasy notation for captured actual type), then the T can be used in a type _expression_ and there is no need to use Unit with the meaning "I am what you want me to be" which is highly specialized in a couple of cases when the mapping from "captured" to "actual" type is known in the implementation. To summarize what i propose: Reserve the name Unit Make grammar accept an empty [] after a type with the meaning that it creates an "empty" type Thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you 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-6090) Output of iterator type results in unhandled exception
Title: Message Title
Henrik Lindberg commented on PUP-6090
Re: Output of iterator type results in unhandled exception
I think that makes it incredibly complex and prevents flowing values through a chain lazily (you would always have to produce the full result as it is only the originating function that knows what it is supposed to return. It also blocks mapping to another type if the original type is involved.
{a => 10, b => 20}.map |$k, $v| { $k }
Should that produce a hash?
I would like the concept of mapped arguments to be generalized though based on entry size, and that if a lambda specifies one additional parameter (over the size of the entry/element) it will get the index. Thus reverse_each when given a block would unfold its entry onto the lambda parameters. If they come from a hash, or an array with tuples should not matter.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6093) Core Windows Type Additions
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6093 Core Windows Type Additions Change By: Rob Reynolds Component/s: Windows Component/s: Types and Providers Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6093) Core Windows Type Additions
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6093 Core Windows Type Additions Change By: Rob Reynolds Labels: types windows Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6093) Core Windows Type Additions
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6093 Core Windows Type Additions Change By: Rob Reynolds Component/s: PE Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-75) Strings calls 'interpret_any' with the wrong number of arguments
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-75 Strings calls 'interpret_any' with the wrong number of arguments Change By: Hailee Kenney Fix Version/s: PDOC 0.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-75) Strings calls 'interpret_any' with the wrong number of arguments
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet Strings / PDOC-75 Strings calls 'interpret_any' with the wrong number of arguments Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-75) Strings calls 'interpret_any' with the wrong number of arguments
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-75 Strings calls 'interpret_any' with the wrong number of arguments Issue Type: Bug Assignee: Unassigned Created: 2016/03/24 2:08 PM Priority: Normal Reporter: Hailee Kenney Puppet strings uses an API private method in puppet which has been updated to take two parameters instead of one. This means strings is calling it with the wrong number of variables in the host class handler which is causing it to crash: https://github.com/puppetlabs/puppetlabs-strings/blob/master/lib/puppet_x/puppetlabs/strings/yard/handlers/host_class_handler.rb#L19 This ticket is for fixing the issue in strings. For details around the fact that strings is using API private puppet methods, see PUP-6088 Add Comment
Jira (PUP-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-6088 Make TypeParser#interpret public API for Puppet Strings use Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5967) File type links documentation incorrectly references :ignore value
Title: Message Title Rob Braden updated an issue Puppet / PUP-5967 File type links documentation incorrectly references :ignore value Change By: Rob Braden Fix Version/s: PUP 4.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2547) Add in new clj-i18n scaffolding to PuppetDB
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2547 Add in new clj-i18n scaffolding to PuppetDB Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Peter Huene commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash This is starting to sound like an implementation detail to me instead of something that needs to be enshrined in the type system specification. I'm not saying we can't use it internally in the Ruby implementation to simplify inference calculations, but perhaps it could simply be displayed as "Any" when we happen to output types containing it (i.e. empty hash/array and default tuple)? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Ethan Brown commented on PUP-6092 Re: Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) There is actually a way to apply conditional logic to workaround the fact that the file type does not support setting attributes using an exec. I would recommend the approach that I've outlined below as it relies on cmd.exe instead of PowerShell, and will therefore execute much more quickly. The dir commands take switches for the attributes which can then be used to query the file system, to ensure idempotency. For instance: C:\>dir /ah c:\pagefile.sys Volume in drive C is Windows 2008 Volume Serial Number is D8AA-E11A Directory of c:\ 03/23/2016 04:33 PM 536,870,912 pagefile.sys 1 File(s)536,870,912 bytes 0 Dir(s) 6,025,601,024 bytes free
Jira (PUP-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Henrik Lindberg commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash In inference if empty is inferred as having type Any, then when computing the commonality of Any and some other type, it regresses to Any. When Unit is used instead of Any, the inference result is the other type. Thus the Unit type is essential in those scenarios. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Henrik Lindberg commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash It is complicated, and as I said, if we do not have to add it I am for doing something different. IIRC the main use is as an inference result, not a type that you would declare and match against. The only reason to include it would be to not reserve any magic to the implementation, and to prevent that Unit in puppet results in a Resource type. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Michael Smith updated an issue Facter / FACT-1284 Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result Change By: Michael Smith Sprint: Client 2016-01-13 , Client 2016-04-20 (Bigga Bugs) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Peter Huene commented on FACT-1284 Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result I'm now leaning towards having Facter 3 set $? for backwards compatibility reasons. I'm about to recommend a Facter 2 user make use of it for what they want to do as it's currently not possible to tell if a command failed its execution without using $?. :on_fail is only used for basically "command not found" scenarios; not for when the process returns non-zero exit code. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Peter Huene updated an issue Facter / FACT-1284 Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result Change By: Peter Huene Fix Version/s: FACT 3.1.7 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title
Paul Anderson updated an issue
Puppet / PUP-6092
Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Change By:
Paul Anderson
Comment:
{{file { 'c:/hidden': ensure => directory,}exec { 'Make hidden': command => 'attrib +h c:/hidden', path => $::path, onlyif => 'if (-Not (Get-ItemPro{{monospaced text}}perty -Path C:\hidden).mode | select-string h) {exit 1}', provider => 'powershell', require => File['c:/hidden'],}Hat tip to [~nate.mccurdy]}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title
Nate McCurdy commented on PUP-6092
Re: Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Here's what we'll end up doing. The DSC module probably would've been cleaner, but the customer prefers not to use DSC due to it's PowerShell5 requirement.
file { 'c:/hidden':
ensure => directory,
}
exec { 'Make hidden':
command => 'attrib +h c:/hidden',
path => $::path,
_onlyif_ => 'if (-Not (Get-ItemProperty -Path C:\hidden).mode | select-string h) {exit 1}',
provider => 'powershell',
require => File['c:/hidden'],
Jira (PUP-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title
Paul Anderson commented on PUP-6092
Re: Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
file { 'c:/hidden': ensure => directory, }
exec { 'Make hidden': command => 'attrib +h c:/hidden', path => $::path, _onlyif_ => 'if (-Not (Get-ItemProperty -Path C:\hidden).mode | select-string h) {exit 1}
', provider => 'powershell', require => File['c:/hidden'], }
Hat tip to Nate McCurdy
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Peter Huene commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash I'm against adding Unit to the specification (plus the name "Unit" is nondescript in its intent and behavior). I see no reason why empty arrays or hashes can't infer to Array[Any, 0, 0] or Hash[Any, 0, 0], but perhaps I'm missing something important. To me, those types mean the array could hold anything, but it's empty. I believe that having yet another type to mean it is an "empty set of type" is redundant in these type signatures. Plus, assuming Unit was fully participating in the type system, what would Array[Unit, 5, 5] mean, exactly? Would that match against [1, 2, 3, 4, 5] exactly like Array[Any, 5, 5] would? Would it only match against empty arrays? If so, would Array[Any, 0, 0] no longer match against an empty array? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Paul Anderson commented on PUP-6092 Re: Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Right now, PS is using work arounds for this. We have to exec out to powershell set these attributes, and there's not a good way to check the attributes to perform conditional logic. It's a hack, it's ugly and the customer doesn't like it. That said, this isn't impacting the delivery schedule for any customer. It's just a feature request at this point. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6090) Output of iterator type results in unhandled exception
Title: Message Title
Peter Huene commented on PUP-6090
Re: Output of iterator type results in unhandled exception
The native implementation currently knows what is being iterated even if you chain iterators together, at least until we have proper functional closures in the language where the block is a part of the iterator itself (e.g. map returning an iterator), potentially transforming the sequence type. At that point, the implementation could base its representation on the "input type" of the iterator instead of the type of the original value being iterated upon, like it does now.
Thus with the native implementation:
notice({ foo => bar, bar => baz }.reverse_each)
notice({ foo => bar, bar => baz }.reverse_each.reverse_each)
outputs (note: it does not create any additional hashes or strings, as one would expect for simply outputting the iterator):
Notice: Scope(Class[main]): {bar => baz, foo => bar}
Notice: Scope(Class[main]): {foo => bar, bar => baz}
I can change this to always output an array representation, but I personally think it makes more sense to represent the output based on the input sequence type (sequence vs. "key-value" sequence).
Additionally, because the iterator tracks whether or not the source is a key-value sequence, this works as one would expect in the native compiler where it currently does not in 4.4.0:
Jira (PUP-6095) Service provider shouldn't die if an smf service is in state "degraded"
Title: Message Title Shawn Ferry created an issue Puppet / PUP-6095 Service provider shouldn't die if an smf service is in state "degraded" Issue Type: Bug Affects Versions: PUP 4.4.0, PUP 3.8.2 Assignee: Shawn Ferry Components: Types and Providers Created: 2016/03/24 11:11 AM Environment: Puppet 3.8.2 Solaris 12 installed from IPS package Priority: Normal Reporter: Shawn Ferry Original Estimate: 1 hour Remaining Estimate: 1 hour
Jira (PUP-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title Henrik Lindberg commented on PUP-6091 Re: Lookup CLI should use unquoted dot in key as sub-lookup I don't understand what is unhelpful about only supporting it in the CLI application - can you elaborate? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6011) Fix line endings in spec/integration/module_tool/tar/mini_spec.rb
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-6011 Fix line endings in spec/integration/module_tool/tar/mini_spec.rb Change By: Glenn Sarti Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Rob Reynolds Labels: scheduled_task Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Rob Reynolds Labels: scheduled_task windows Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6087) Multiple contradictory 'consumes' annotation do not lead to an error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6087 Multiple contradictory 'consumes' annotation do not lead to an error Change By: Henrik Lindberg Scrum Team: Application Orchestration Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6067) Pip3 provider does not include features from Pip
Title: Message Title Rob Braden updated an issue Puppet / PUP-6067 Pip3 provider does not include features from Pip Change By: Rob Braden Release Notes Summary: Package provider features were not inherited from the parent provider. This adds features provided by Pip as also provided by Pip3. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Henrik Lindberg commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash I think it should be made into a bona fide type in the type system. There is a difference between Any and Unit, and without the Unit type special cases are needed in a couple of places (i.e. length alters type). IIRC there is also a case when dealing with lambdas, but I don't remember the details there. The reason we are not handling Unit in the type parser is a bug IMO. I am however open to doing things differently here. Ping Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1376) {{facter -h}} should be equivalent to {{facter --help}}
Title: Message Title
Michael Smith created an issue
Facter / FACT-1376
{{facter -h}} should be equivalent to {{facter --help}}
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2016/03/24 10:55 AM
Priority:
Normal
Reporter:
Michael Smith
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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,
Jira (PUP-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}
Title: Message Title
Michael Smith created an issue
Puppet / PUP-6094
{{puppet -h|--help}} should be equivalent to {{puppet help}}
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2016/03/24 10:55 AM
Priority:
Normal
Reporter:
Michael Smith
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PUP-5877) acceptance: puppet class inheritance
Title: Message Title Rob Braden updated an issue Puppet / PUP-5877 acceptance: puppet class inheritance Change By: Rob Braden Fix Version/s: PUP 4.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title Thomas Hallgren commented on PUP-6091 Re: Lookup CLI should use unquoted dot in key as sub-lookup This acceptance criteria is unclear: It is possible to perform a sub-lookup using the lookup CLI by not quoting, e.g. ahash.some_key because it assumes that Lookup can deal with dotted keys. It cannot. And while we certainly could implement this at the very top, that wouldn't be very helpful for people expecting that subkey lookup results are subject to merging. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6011) Fix line endings in spec/integration/module_tool/tar/mini_spec.rb
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6011 Fix line endings in spec/integration/module_tool/tar/mini_spec.rb Change By: Ethan Brown Sprint: Windows 2016-04- 20 06 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6093) Core Windows Type Additions
Title: Message Title Ethan Brown created an issue Puppet / PUP-6093 Core Windows Type Additions Issue Type: Epic Assignee: Unassigned Created: 2016/03/24 10:49 AM Priority: Normal Reporter: Ethan Brown Any functionality gaps present in core types when compared to other similar tools. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6092 Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Change By: Ethan Brown Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6092 Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Change By: Ethan Brown Component/s: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1441) --show_diff causes crashes on files with UTF-8 content
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1441 --show_diff causes crashes on files with UTF-8 content Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Peter Huene commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash The type is not documented in the specification and its use makes little sense to me; we already describe the emptiness of the array with the bounds, there is no need for an "nothing" type. If Unit worked the way you describe, why does [foo, bar] =~ Array[Unit] evaluate to false? I suspect it is because we're treating Unit like a resource type. If that is the case, Unit really is an internal implementation detail and should not be leaking into the actual type system. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6090) Output of iterator type results in unhandled exception
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6090 Output of iterator type results in unhandled exception Change By: Henrik Lindberg Sprint: Language Triage 2016-04-20 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6090) Output of iterator type results in unhandled exception
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6090 Output of iterator type results in unhandled exception Change By: Henrik Lindberg Fix Version/s: PU 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6090) Output of iterator type results in unhandled exception
Title: Message Title Henrik Lindberg commented on PUP-6090 Re: Output of iterator type results in unhandled exception The error in the ruby implementation is that notice (which is a kind of to-string transformer) function should do a to_a before producing output. Peter Huene as the notion of "being an array or hash" is lost when seeing an Iterator, I suggest the native output to always be an array in string form. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6090) Output of iterator type results in unhandled exception
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6090 Output of iterator type results in unhandled exception Change By: Henrik Lindberg Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Craig Gomes commented on PUP-6092 Re: Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Maybe Sean or John from RE too Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Paul Anderson commented on PUP-6092 Re: Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Craig Gomes is unavailable for a few days and suggested that Ethan Brown may be able to put eyes on this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Henrik Lindberg commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash It can be viewed as the undef of types. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Henrik Lindberg commented on PUP-6089 Re: type function: Unit type being returned for empty array and hash Unit is part of the Puppet Type system. Unit means "whatever you want it to be" (which includes "nothing"). There is a difference to accepting Any which means it must be something - Unit accepts "nothingness" as well. It is not the best specified of types in the type system, but it is part of it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6011) Fix line endings in spec/integration/module_tool/tar/mini_spec.rb
Title: Message Title Ethan Brown commented on PUP-6011 Re: Fix line endings in spec/integration/module_tool/tar/mini_spec.rb Merged to master in https://github.com/puppetlabs/puppet/commit/11970d4f221f3c7b13dc5aa3e8d03525a0531f13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5990) Lookup data provider should allow dot in %{key.subkey} to be escaped
Title: Message Title
Henrik Lindberg commented on PUP-5990
Re: Lookup data provider should allow dot in %{key.subkey} to be escaped
Thomas Hallgren lets keep that discussion on PUP-6091. (The intent is not to let it bleed through to every level).
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-33) Implement support for the Iterator type
Title: Message Title Henrik Lindberg assigned an issue to qa Native Puppet / NPUP-33 Implement support for the Iterator type Change By: Henrik Lindberg Status: Ready for Merge Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-33) Implement support for the Iterator type
Title: Message Title Henrik Lindberg commented on NPUP-33 Re: Implement support for the Iterator type Merged to master: b7d1689 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6092 Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Change By: Kylo Ginsberg Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Kylo Ginsberg assigned an issue to Craig Gomes Puppet / PUP-6092 Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Craig Gomes Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Kylo Ginsberg commented on PUP-6092 Re: Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Ping Craig Gomes Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Paul Anderson created an issue Puppet / PUP-6092 Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) Issue Type: New Feature Affects Versions: PUP 4.4.0 Assignee: Kylo Ginsberg Components: Client Created: 2016/03/24 10:09 AM Environment: A Windows system with a file or folder with the hidden attribute set, e.g. C:\hidden Puppet agent installed Priority: Normal Reporter: Paul Anderson Puppet describe file "c:\hidden" does not provide any way to identify if that file is hidden. In Linux, identifying hidden files is .trivial and not an attribute. However, the Windows platform does this very differently. The file provider for windows (whether POSIX or Windows, i'll let the Dev's decide) should indicate the relevant attributes, including its hidden-ness, archive-iness, etc. Additionally, the ability to easily set these attributes would be nice, rather than having to call an exec to powershell, attrib.exe, etc.
Jira (NPUP-32) Implement support for the Iterable type
Title: Message Title Henrik Lindberg assigned an issue to qa Native Puppet / NPUP-32 Implement support for the Iterable type Change By: Henrik Lindberg Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-508) Subkeys can be matched by string values that contain the subkey.
Title: Message Title Henrik Lindberg commented on HI-508 Re: Subkeys can be matched by string values that contain the subkey. merged to master at: ef4f0de Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6085) Subkeys can be matched by string values that contain the subkey.
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6085
Subkeys can be matched by string values that contain the subkey.
Change By:
Henrik Lindberg
A subkey of a dotted key can be matched by a string that contains the key. Given the following data (yaml):{code:yaml}---foo: bar{code}a lookup of the key 'foo.bar' will produce 'bar'. This happens because the data provider asks if the value responds to {{:\[\]}} and a ruby {{String}} will. Then {{"bar"\["bar"\]}} returns {{"bar"}}. ACCEPTANCE CRITERIA* that a lookup of {{foo.bar}} does not produce {{'bar'}} when the key {{foo}} is bound to the string {{'bar'}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6085) Subkeys can be matched by string values that contain the subkey.
Title: Message Title Henrik Lindberg commented on PUP-6085 Re: Subkeys can be matched by string values that contain the subkey. And to master at: cd65b1b Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6085) Subkeys can be matched by string values that contain the subkey.
Title: Message Title Henrik Lindberg commented on PUP-6085 Re: Subkeys can be matched by string values that contain the subkey. merged to stable at: e3e4ba8 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-508) Subkeys can be matched by string values that contain the subkey.
Title: Message Title Henrik Lindberg commented on HI-508 Re: Subkeys can be matched by string values that contain the subkey. And to master at: da6579e Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1913) Puppet user resource should respect the forcelocal option
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1913 Puppet user resource should respect the forcelocal option Change By: Kylo Ginsberg Sprint: Client 2016-04-20 (Bigga Bugs) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1913) Puppet user resource should respect the forcelocal option
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1913 Puppet user resource should respect the forcelocal option Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5233) puppet inspect is using wrong path for catalog data
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-5233
puppet inspect is using wrong path for catalog data
Change By:
Michael Smith
Release Notes Summary:
In Puppet 3 the catalog cache end-point changed to JSON, but {{puppet inspect}} was not updated to take that into account. Fix {{puppet inspect}} so it successfully finds the cached catalog. There are still known issues with {{inspect}} (PUP-6041).
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5233) puppet inspect is using wrong path for catalog data
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-5233
puppet inspect is using wrong path for catalog data
Change By:
Michael Smith
Release Notes Summary:
In Puppet 3 the catalog cache end-point changed to JSON, but {{puppet inspect}} was not updated to take that into account. Fix {{puppet inspect}} so it successfully finds the cached catalog.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title Henrik Lindberg commented on PUP-6091 Re: Lookup CLI should use unquoted dot in key as sub-lookup Confused; data from a data provider must be able to have dots in the keys, and lookup of keys using the lookup function treats keys as verbatim (i.e. Puppet API is unchanged). The only change is that the Lookup CLI adds support for slicing. What in the acceptance criteria (now slightly updated) is unclear? Is this a request to make the Hiera interpolation logic with dotted names et al, the general mechanism for lookup? Only for the lookuo CLI, not for Puppet API. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6091
Lookup CLI should use unquoted dot in key as sub-lookup
Change By:
Henrik Lindberg
In PUP-5990 it was made possible to quote dot in a key to do a verbatim lookup. The Lookup CLI however always treats the given key as a verbatim key and does not provide a way to further slice the returned value.The command line {{lookup}} should be made consistent with hiera and facter tools as they take unquoted input as sub-lookup, and handles quoted input as verbatim.This feature only applies to the {{lookup}} CLI, the API from Puppet should remain unchanged.ACCEPTANCE CRITERIA* It is possible to lookup a verbatim key using the lookup CLI by quoting it . e.g. 'foo.bar'* It is possible to perform a sub-lookup using the lookup CLI by not quoting, e.g. ahash.some_key* Puppet API is unaffected - i.e. {{lookup('foo.bar')}} returns the same as before the change
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Rob Braden commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Are there release notes for this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6089) type function: Unit type being returned for empty array and hash
Title: Message Title Rob Braden updated an issue Puppet / PUP-6089 type function: Unit type being returned for empty array and hash Change By: Rob Braden Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title Thomas Hallgren commented on PUP-6091 Re: Lookup CLI should use unquoted dot in key as sub-lookup Please note that PUP-5990 only applies to the Hiera data provider. Dotted keys are not applicable anywhere else (not even as keys in the Hiera data provider). The only place where they can be used presently is in a Hiera data provider interpolated value. Is this a request to make the Hiera interpolation logic with dotted names et al, the general mechanism for lookup? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6090) Output of iterator type results in unhandled exception
Title: Message Title Rob Braden updated an issue Puppet / PUP-6090 Output of iterator type results in unhandled exception Change By: Rob Braden Fix Version/s: PUP 4.4.1 Fix Version/s: PUP 4.4.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-508) Subkeys can be matched by string values that contain the subkey.
Title: Message Title Henrik Lindberg commented on HI-508 Re: Subkeys can be matched by string values that contain the subkey. merged to stable at: 318c398 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-508) Subkeys can be matched by string values that contain the subkey.
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-508
Subkeys can be matched by string values that contain the subkey.
Change By:
Henrik Lindberg
A subkey of a dotted key can be matched by a string that contains the key. Given the following hiera (yaml):{code:yaml}---foo: bar{code}a lookup of the key 'foo.bar' will produce 'bar'. This happens because Hiera asks if the value responds to {{:\[\]}} and a ruby {{String}} will. Then {{"bar"\["bar"\]}} returns {{"bar"}}. ACCEPTANCE CRITERIA* that a lookup of {{foo.bar}} does not produce {{'bar'}} when the key {{foo}} is bound to the string {{'bar'}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6028) Treat unresolved type references as errors instead of being a Resource type
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6028 Treat unresolved type references as errors instead of being a Resource type Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6053) type mismatch error involving struct member should quote member name
Title: Message Title Henrik Lindberg commented on PUP-6053 Re: type mismatch error involving struct member should quote member name Merged to master at: Make TypeMismatchDescriber discover unresolved types Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6028) Treat unresolved type references as errors instead of being a Resource type
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6028
Treat unresolved type references as errors instead of being a Resource type
Change By:
Henrik Lindberg
References to resource types are not validated against existing types. Now all non data types are considered to be a Resource type. The introduction of type aliases makes it possible to validate all references to types. By fixing this all references to undefined types will be caught everywhere not just when attempting to create a resource of that type, as is the case today.With the addition of type aliases and being able to load types using the 4.x loaders to resolve types it should be relatively easy to add every known resource type as an alias to a Resource. (if we are not already doing that; in which case it is as easy as changing the default of treating 'unknown' as a Resource to as a 'not found'; if so change the # story points).ACCEPTANCE CRITERA* all references to undefined types raises an error during compilation* * trivially tested by {{$a = SantaClause}} and {{$b = ToothFairy\['emea']}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6053) type mismatch error involving struct member should quote member name
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6053
type mismatch error involving struct member should quote member name
Change By:
Henrik Lindberg
With this function definitinon:{code:ruby} local_types dotype 'Radix = Variant[Default, Integer[2,2], Integer[8,8], Integer[10,10], Integer[16,16]]'type 'Convertible = Variant[Undef, Integer, Float, Boolean, String]'type 'NamedArgs = Struct[{from => Convertible, Optional[radix] => Radix}]' end dispatch :from_named_args doparam 'Convertible', :fromoptional_param 'Radix', :radix end dispatch :from_hash doparam 'NamedArgs', :hash_args end{code}And calling it with:{code:puppet}the_function({from => 10, radix => 3}){code}The error message is:{code}rejected: parameter 'hash_args' struct member radix expects a value of type...{code}I expected the member name to be quoted like this:{code}rejected: parameter 'hash_args' struct member 'radix' expects a value of type...{code}In this case it was readable without the quotes, but not when the struct member name issomething like 'or', 'and', 'struct', 'expects', or 'not rejected' :-) ACCEPTANCE CRITERIA* That the following example quotes the name {{'always'}}{code:puppet}puppet apply -e 'function example(Struct[{always => Integer[100]}] $x) { }; example({always =>3})'{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To
Jira (PUP-6028) Treat unresolved type references as errors instead of being a Resource type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6028 Treat unresolved type references as errors instead of being a Resource type Change By: Henrik Lindberg Release Notes Summary: References to resource types are now validated against existing types. Earlier all non data types were considered to be a Resource type. The introduction of type aliases made it possible to validate all type references to types . This means that references to undefined types will be caught everywhere during compilation not just when attempting to create a resource of that type or when forming a relationship . Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6028) Treat unresolved type references as errors instead of being a Resource type
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6028
Treat unresolved type references as errors instead of being a Resource type
Change By:
Henrik Lindberg
References to resource types are not validated against existing types. Now all non data types are considered to be a Resource type. The introduction of type aliases makes it possible to validate all references to types. By fixing this all references to undefined types will be caught everywhere not just when attempting to create a resource of that type, as is the case today.With the addition of type aliases and being able to load types using the 4.x loaders to resolve types it should be relatively easy to add every known resource type as an alias to a Resource. (if we are not already doing that; in which case it is as easy as changing the default of treating 'unknown' as a Resource to as a 'not found'; if so change the # story points). ACCEPTANCE CRITERA* all references to undefined types raises an error during compilation** trivially tested by {{$a = SantaClause}} and {{$b = ToothFairy\['emea']}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5990) Lookup data provider should allow dot in %{key.subkey} to be escaped
Title: Message Title
Thomas Hallgren commented on PUP-5990
Re: Lookup data provider should allow dot in %{key.subkey} to be escaped
Henrik Lindberg, that means that we let Hiera semantics leak into the lookup command at every level. Do we want that? I did ask this when the hiera data provider was implemented and the interpolation support was added. At that time, the answer was no. We don't want that. So what changed?
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-6091
Lookup CLI should use unquoted dot in key as sub-lookup
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/03/24 7:26 AM
Priority:
Normal
Reporter:
Henrik Lindberg
In
PUP-5990
it was made possible to quote dot in a key to do a verbatim lookup. The Lookup CLI however always treats the given key as a verbatim key and does not provide a way to further slice the returned value.
The command line lookup should be made consistent with hiera and facter tools as they take unquoted input as sub-lookup, and handles quoted input as verbatim.
This feature only applies to the lookup CLI, the API from Puppet should remain unchanged.
ACCEPTANCE CRITERIA
It is possible to lookup a verbatim key using the lookup CLI by quoting it . e.g. 'foo.bar'
It is possible to perform a sub-lookup by not quoting, e.g. ahash.some_key
Puppet API is unaffected - i.e. lookup('foo.bar') returns the same as before the change
Jira (PUP-5990) Lookup data provider should allow dot in %{key.subkey} to be escaped
Title: Message Title
Henrik Lindberg commented on PUP-5990
Re: Lookup data provider should allow dot in %{key.subkey} to be escaped
Francois Lafont Logged PUP-6091 to change the lookup CLI (and I agree with your assessment of what is best).
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup CLI should use unquoted dot in key as sub-lookup
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6091 Lookup CLI should use unquoted dot in key as sub-lookup Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6053) type mismatch error involving struct member should quote member name
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6053 type mismatch error involving struct member should quote member name Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6088
Make TypeParser#interpret public API for Puppet Strings use
Change By:
Henrik Lindberg
The puppet strings tool currently relies on at least one (potentially more) methods in puppet that are API private. This can lead to weird breakages in strings that are kind of mysterious since API private methods can be changed at will. The current issue in question is this one:https://github.com/puppetlabs/puppetlabs-strings/blob/master/lib/puppet_x/puppetlabs/strings/yard/handlers/host_class_handler.rb#L19An API private method was being used for parameter type checking, and was updated to require two parameters instead of one. This created a kind of mysterious error in strings and situations like this aren't ideal. So we need to answer two questions (which may have the same answer):# What do we want to do with this error specifically?# How do we want to handle strings using API private methods? UPDATEMake {{TypeParser#interpret}}, and {{#interpret_any}} methods {{@api public}} to avoid a future regression.ACCEPTANCE CRITERIAThe ruby source for the methods in question show that they are {{@api public}}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6088 Make TypeParser#interpret public API for Puppet Strings use Change By: Henrik Lindberg Story Points: 1 Sprint: Language Triage Scrum Team: Language Release Notes: Not Needed Fix Version/s: PUP 4.5.0 Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
