Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Thomas Hallgren commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Given that the patch makes things "crazy slow", I would avoid implementing the patch. I think there's a fair chance that the slowness hits a lot of customers and the reason for it is forgotten. Raise the priority on this ticket if needed, but the root cause must be dealt with. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302978.1554294806000.10704.1580742840391%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Thomas Hallgren commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Looking at Trevor's functional workaround, I can only concur with Henrik's assessment earlier: "What happens is that it probably ended up with a mix of loading both the generated types and the actual resource type implementations. The agent most certainly needs to load the resource type implementations and should ignore the generated types completely". That would also explain at least part of the slow down. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302978.1554294806000.9507.1580595900215%40Atlassian.JIRA.
Jira (PUP-10259) Hiera cannot interpolate non-string values
Title: Message Title Thomas Hallgren commented on PUP-10259 Re: Hiera cannot interpolate non-string values In this case (looking up an alias), the argument is needed to declare what alias to look up. How would that be declared otherwise. Just passing the original key doesn't help much unless the actual function knows about aliases. But if so, where does it get that info? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.244421.1522942982000.4290.1580295540903%40Atlassian.JIRA.
Jira (PUP-10259) Hiera cannot interpolate non-string values
Title: Message Title
Thomas Hallgren commented on PUP-10259
Re: Hiera cannot interpolate non-string values
Using a lookup_option to appoint a lookup_key style function would certainly work, and would be a nice feature to have but having a strict interpolation that propagates "not found" would be really nice too. It is probably easier to learn for the user since it relies on an already established pattern. Compare these:
lookup_options:
docker::selinux_enabled:
delegate_to: strict_scope
docker::selinux_enabled: "%{strict('facts.selinux.enabled')}"
and consider that the familiar pattern that we are trying to fix without making a breaking change, is this:
docker::selinux_enabled: "%{'facts.selinux.enabled'}"
Adding a `strict` function to the current set of interpolation functions is also less effort for us to implement. The current logic is fully recursion protected. We must improve that protection if we decide to implement an ability to call arbitrary function.
Jira (PUP-8593) Add alias to lookup_options and make it redirect to lookup of the alias
Title: Message Title Thomas Hallgren commented on PUP-8593 Re: Add alias to lookup_options and make it redirect to lookup of the alias Not sure why that is. The only thing that the current alias doesn't, is to propagate the "not-found" condition. It preserves the type and it guards against recursion. Perhaps I'm missing something but besides the "advanced features" (which I personally think we should avoid), I don't see more value added here. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242722.1521802594000.3263.1580239260216%40Atlassian.JIRA.
Jira (PUP-10251) Feature request: Add a way to turn looked up undef values in Hiera into "not found"
Title: Message Title Thomas Hallgren commented on PUP-10251 Re: Feature request: Add a way to turn looked up undef values in Hiera into "not found" Yes, of course. I meant "not-found", not undef. Doh! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343178.1579803772000.3254.1580238840543%40Atlassian.JIRA.
Jira (PUP-10259) Hiera cannot interpolate non-string values
Title: Message Title Thomas Hallgren moved an issue Puppet / PUP-10259 Hiera cannot interpolate non-string values Change By: Thomas Hallgren Key: HI PUP - 599 10259 Project: Hiera Puppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.244421.1522942982000.3177.1580237340575%40Atlassian.JIRA.
Jira (HI-599) Hiera cannot interpolate non-string values
Title: Message Title
Thomas Hallgren commented on HI-599
Re: Hiera cannot interpolate non-string values
Perhaps we should have something identical to the strict_alias proposed in PUP-8593?. Given that an interpolation without any function is identical to scope, we could make strict imply a strict lookup in scope. E.g.
docker::selinux_enabled: "%{strict('facts.selinux.enabled')}"
would give the desired result.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.244421.1522942982000.3157.1580237280323%40Atlassian.JIRA.
Jira (PUP-10251) Feature request: Add a way to turn looked up undef values in Hiera into "not found"
Title: Message Title Thomas Hallgren commented on PUP-10251 Re: Feature request: Add a way to turn looked up undef values in Hiera into "not found" Henriks example results in an empty string. The strict_alias proposed in PUP-8593 would result in an undef. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343178.1579803772000.3148.1580236920223%40Atlassian.JIRA.
Jira (PUP-8593) Add alias to lookup_options and make it redirect to lookup of the alias
Title: Message Title Thomas Hallgren commented on PUP-8593 Re: Add alias to lookup_options and make it redirect to lookup of the alias A simpler, and perhaps more straight forward solution that was proposed in PUP-8341, is to introduce an additional interpolation function. This has already been done in the Go version of Hiera. The function is called `strict_alias` and behaves like `alias` with the exception that a not found is propagated instead of translated into an empty string. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242722.1521802594000.3121.1580236440635%40Atlassian.JIRA.
Jira (PUP-10233) environment_classes API endpoint extremely slow
Title: Message Title Thomas Hallgren commented on PUP-10233 Re: environment_classes API endpoint extremely slow One option here could be to use a Go puppet parser. It has way better performance than the Ruby parser and would be pretty easy to also make multi-threaded. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341970.157901085.29528.1579462800167%40Atlassian.JIRA.
Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity
Title: Message Title Thomas Hallgren commented on PUP-10210 Re: puppet fails with JSON error when a fact value equals Infinity I agree. Float["infinity"], Float["-infinity"], and Float["NaN"] should be made to match their corresponding float values. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340709.1577387077000.14149.1578401580159%40Atlassian.JIRA.
Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity
Title: Message Title
Thomas Hallgren commented on PUP-10210
Re: puppet fails with JSON error when a fact value equals Infinity
Float::INFINITY is of type Float, both in Ruby and in most other languages. I don't see anything wrong in treating it as a Float in Pcore too. Further more, many serialization formats, including YAML, can handle both NaN and infinity. The way I see it, this is only a problem when serializing using JSON and as such, it doesn't motivate a new data type. The best solution is to improve the Pcore rich-data serialization specifically for JSON so that the values NaN, infinity, and negative infinity are serialized using:
{ "__ptype": "Float", "__pvalue": "NaN"},{ "__ptype": "Float", "__pvalue": "infinity"}, { "__ptype": "Float", "__pvalue": "-infinity"}
i.e. no new data type, just force use of strings on the Float data type.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop
Jira (PUP-9932) Make 3x functions loaders thread-safe
Title: Message Title Thomas Hallgren commented on PUP-9932 Re: Make 3x functions loaders thread-safe Making the Puppet runtime threadsafe is something that would strongly advice against with a huge red flag. Do not do this! There is nothing in the runtime today that was created with concurrency in mind and there's a whole slew of shared resources that would need to be protected in order for this to work. For instance, there's just no way that threads can share the same set of loaders. Not only are the loaders themselves unsafe but also most of the objects that they load. Several objects cached values on demand. Nothing in there takes into account that multiple threads may access these objects simultaneously. The hiera lookup system is not threadsafe. The serialization is not threadsafe. The parser is not thread safe. And so on and so forth (because nothing is). The really horrible thing is that even if all of the Puppet runtime is really made threadsafe, the next problem is that no code in any module was even been written with concurrency in mind. No module out there can be considered not threadsafe. Also, what about the third party gems that puppet make use of? Do they declare that they are safe to use in a threaded environment? If they don't, then rest assured that they cannot. I think that a much safer approach would be to abandon the use of JRuby and instead direct all resources to use a pool of MRI instances. They can be initialized some degree (initial set of classes loaded etc.) and there must be a reset to that wellknown state after a pooled instance has been used. But there would be absolutely no threading going on. I wasn't aware of the work of making the Puppet runtime threadsafe until yesterday, hence my late input on this. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Thomas Hallgren commented on PUP-10113 Re: Functions are slower if called with chained syntax than with prefix syntax Just a side note regarding type inference. Perhaps it would be worth investigating a concept I called "exact types" in dgo. In essence, an exact type is a type that is backed by the value that it represents. Complex types like map, array, etc. always return that kind of type which means that very little copying is made in order to determine the type of a value. A full test if such a type is assignable to another type is the same thing as asking if the value that it represents is an instance of the that type. I don't think it's trivial to do this in Puppet but it's probably doable without too much of an effort. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.13535.1572463800405%40Atlassian.JIRA.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Thomas Hallgren commented on PUP-10113 Re: Functions are slower if called with chained syntax than with prefix syntax It's likely that we have the same performance issue in pops/evaluator/access_operator.rb (method accessObject line 31). I think a specialized infer_callable (or similar name) method that would return nil in case the given value don't have that such a type could make a lot of difference. AFAICT, only PObjectType, PObjectTypeExtension and PURIType implements TypeWithMembers. The current @api private method TypeCalculator.infer_Object could serve as model for this new method. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.8852.1572276540093%40Atlassian.JIRA.
Jira (PUP-10105) regression: puppet resource --to_yaml should not emit puppet class tags
Title: Message Title Thomas Hallgren commented on PUP-10105 Re: regression: puppet resource --to_yaml should not emit puppet class tags I think it makes sense to use instance_of? in all types that describe both Data and RichData. They must not include subclasses of anything. A subclass that wishes to participate in serialization needs to become a puppet type of some sort, typically an Object. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.329731.1571238944000.4637.1571287500109%40Atlassian.JIRA.
Jira (PUP-10029) A Puppet::DataTypes::Error#to_s() fails with a stack overflow
Title: Message Title Thomas Hallgren commented on PUP-10029 Re: A Puppet::DataTypes::Error#to_s() fails with a stack overflow The code doesn't understand that Puppet::Datatypes::Error is a known type. Does the same thing happen if you precede this with require 'puppet/datatypes' (that's where the type registration happens)? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325693.1569277631000.110990.1569328140298%40Atlassian.JIRA.
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8499 puppet lookup cli, using --facts and --node simultaneously breaks Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.238867.1519838722000.13635.1558421700299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9695) Add ability to return multiple named values from a function.
Title: Message Title Thomas Hallgren commented on PUP-9695 Re: Add ability to return multiple named values from a function. I don't think that a function that declares multiple return values like this should ever be able to return an undef. It will always return a hash containing the values of the variables. This is analog with a function that declares that the returned type is a Struct. It's not allowed to return undef. Just calling return() without arguments should mean "return here using whatever value that the variables have at this point". The sole purpose of doing that is to break out of the function at some other place than at the end. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307734.155731940.27768.1557347760815%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9695) Add ability to return multiple named values from a function.
Title: Message Title Thomas Hallgren commented on PUP-9695 Re: Add ability to return multiple named values from a function. Not sure if it makes sense to be able to narrow the returned type when passing a parameter, given that the passed variable is immutable. I think allowing defaults would be a good thing. Without it, defaults must be explicitly stated within the function itself and perhaps in multiple places. That can be a tedious task since the parameter is immutable. It should be allowed to call return(), but only without arguments. We could allow returning a hash but I don't really see the point in that and it introduces new questions. What if the hash contains more variables? Is that allowed? If it contains fewer variables? Will the declared variable be used in that case? Etc. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307734.155731940.26877.1557334260203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9695) Add ability to return multiple named values from a function.
Title: Message Title
Thomas Hallgren created an issue
Puppet / PUP-9695
Add ability to return multiple named values from a function.
Issue Type:
New Feature
Assignee:
Unassigned
Components:
Language
Created:
2019/05/08 5:43 AM
Priority:
Normal
Reporter:
Thomas Hallgren
This is inspired from Golang where it is possible to return several values from a function and also to declare variables as part of the declaration of the return value. Consider the following function:
function multiReturn() >> Struct[a=>String,b=>Integer] {
$a = 'hello'
$b = 3
return { a => $a, b => $b }
}
Jira (PUP-9693) Hiera Lookup Fails when convert_to is used
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-9693 Hiera Lookup Fails when convert_to is used Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307503.1557191729000.24173.1557205980249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9692) Passwords not redacted in debug mode
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-9692 Passwords not redacted in debug mode Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9560) Class references in Hiera data: parsing error?
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-9560 Class references in Hiera data: parsing error? Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9560) Class references in Hiera data: parsing error?
Title: Message Title Thomas Hallgren commented on PUP-9560 Re: Class references in Hiera data: parsing error? A stack trace from the agent would tell us the origin of the error and the execution path that led up to it. Would it be possible to attach that to this ticket? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9498) Calling hiera first nullifies lookup_options.
Title: Message Title Thomas Hallgren commented on PUP-9498 Re: Calling hiera first nullifies lookup_options. Not really. A theory though. The first call perhaps caches more data than it should based on the Hiera 3 semantics used by the hiera() call. Subsequent lookup() calls return from the cache and therefore seemingly without caring about lookup options in modules. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9191) Provide a mode for puppet lookup where it only returns information on what was found
Title: Message Title Thomas Hallgren commented on PUP-9191 Re: Provide a mode for puppet lookup where it only returns information on what was found I don't think there are any gotchas. It should be a matter of adding an additional flag to the explain support and simply filter out all "not found" info. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9079) Rich data tags __ptype and __pvalue must not be allowed as attribute names
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-9079 Rich data tags __ptype and __pvalue must not be allowed as attribute names Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9079) Rich data tags __ptype and __pvalue must not be allowed as attribute names
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-9079 Rich data tags __ptype and __pvalue must not be allowed as attribute names Issue Type: Bug Assignee: Unassigned Created: 2018/08/24 12:08 AM Priority: Normal Reporter: Thomas Hallgren An attempt to use the rich data tag '__ptype' as the name of an attribute in an Object will cause a failure to serialize that object using the human readable Data format. An Object is represented as a Hash where '__ptype' is supposed to be a String representation of the type and an attribute using the same name causes the type to be overwritten. Use of '__pvalue' will cause a similar confusion when reading the `Object`. The special rich data tags'__ptype' and '__pvalue' should not be permitted as names of attributes in an Object. Add Comment
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Thomas Hallgren commented on PUP-8597 Re: Modify rich data serialization to use shorter tags instead of __pcore_type__ Josh Cooper, I don't think any formal specification has been written yet. I created ticket PUP-9070. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9070) Add formal specification of rich-data serialization to the puppet-specifications repo
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-9070 Add formal specification of rich-data serialization to the puppet-specifications repo Issue Type: New Feature Assignee: Unassigned Created: 2018/08/16 2:47 AM Priority: Normal Reporter: Thomas Hallgren We lack a formal specification of the Puppet Serialization. It should contain both the binary serialization described in Puppet Core Model and Serialization Overview and a description of the hash representation created by the Puppet::Pops::Serialization::ToDataConverter. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8529) Remove data_binding_terminus setting
Title: Message Title Thomas Hallgren commented on PUP-8529 Re: Remove data_binding_terminus setting As Henrik points out, only none `hiera_xxx` calls will use the configured data binding terminus for the lookup. The `hiera_xxx` calls will bypass the terminus and use the global provider directly. That answers Josh Cooper's question with a: "no, this ticket is not blocked". To answer Henrik Lindberg's question, AFAICT, we only have two data_binding_terminus configured. "hiera" and "none", and both are trapped before the terminus is called upon. So the only chance of anything happening here is if someone has installed some external data_binding_terminus. If the objective is to remove this terminus due to long standing deprecation, then I don't see any problems with that. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8615) sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8615 sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice Change By: Thomas Hallgren Fix Version/s: PUP 5.5.3 Fix Version/s: PUP 5.5.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8606 Module-defined data types are very verbose when displayed Change By: Thomas Hallgren Fix Version/s: PUP 5.5.3 Fix Version/s: PUP 5.5.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8959) FastGettext.default_text_domain order dependent test failure
Title: Message Title Thomas Hallgren commented on PUP-8959 Re: FastGettext.default_text_domain order dependent test failure Josh Cooper I get the same error using that command on commit b811907. The parent commit cee544a however, succeeds without error. The culprit commit is part PR-6796 on ticket PUP-8672. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8959) FastGetext.default_text_domain appears to be unset
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8959 FastGetext.default_text_domain appears to be unset Issue Type: Bug Assignee: Unassigned Created: 2018/06/26 2:01 AM Priority: Normal Reporter: Thomas Hallgren When running bundle exec rake parallel:spec[12] from the puppet master branch on a Fedora Linux (I've tested 27 and 28) the following statement: FastGettext.translation_repositories[FastGettext.default_text_domain] returns nil which results in the message "undefined method `chain' for nil:NilClass" in file lib/puppet/gettext/config.rb on line 179. This in turn, causes +40 spec test failures. Sample stack trace from one of the failed tests: 1) Puppet::Resource::Catalog::Compiler when initializing should cache the server metadata and reuse it Failure/Error: puppet_translations = FastGettext.translation_repositories[FastGettext.default_text_domain].chain
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title Thomas Hallgren commented on PUP-8606 Re: Module-defined data types are very verbose when displayed On PTO. Will take a look next week. Den tor 21 juni 2018 22:08Michael Smith (JIRA) < Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Thomas Hallgren commented on PUP-8597 Re: Modify rich data serialization to use shorter tags instead of __pcore_type__ Merged to master at e3723a0. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8597 Modify rich data serialization to use shorter tags instead of __pcore_type__ Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8887 puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Henrik Lindberg, the commit that breaks this workflow, can it be reverted? Judging from the comment, it's an optimization. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml The example seems incomplete. I don't understand how the above code can produce the notice: roles: [firstrole, secondrole] Where did that array come from? Lookup will not find a 'roles' key in any of the listed data files and the provided default value is an empty array. I get the impression that $roles gets its value from a lookup and then is used to actually configure lookup. If that's true, then it's classic chicken-and-egg problem. Constructs like that should be avoided at length. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For
Jira (PUP-7822) Add a get() function that supports dot syntax to "dig" into hash/array
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7822 Add a get() function that supports dot syntax to "dig" into hash/array Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7822) Add a get() function that supports dot syntax to "dig" into hash/array
Title: Message Title Thomas Hallgren commented on PUP-7822 Re: Add a get() function that supports dot syntax to "dig" into hash/array Merged to master at 7a5db8d. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Thomas Hallgren commented on PUP-8766 Re: puppet device fails with undefined method `loaders' for nil:NilClass when env is not production The problem is that this line: env = Puppet.lookup(:environments).get(Puppet[:environment]) results in env being nil. AFAICT, that can only happen when given the environment doesn't exist. Testing the command with --environment= works OK. So I'm lowering the priority on this one. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8766 puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Change By: Thomas Hallgren Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Thomas Hallgren commented on PUP-8766 Re: puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Please run the command with --trace and attach the stacktrace for the error. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title
Thomas Hallgren commented on PUP-8744
Re: Using a variable in a Type on a parameter results in an error unless the variable was already loaded
If someone would want to do dynamic checking, that is possible, but it must be done in code (of course, since it's dynamic). A type can be parsed from a String. Example where $myvar is a regexp:
$the_type = Type("Pattern[$myvar]")
$value = $the_type.assert_type($value)
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title Thomas Hallgren commented on PUP-8744 Re: Using a variable in a Type on a parameter results in an error unless the variable was already loaded Yes, I agree with that. The type declaration is a static construct so allowing non-literals is a bug. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8728) A parameter that does not pass type validation can cause catalog compilation failure if used in the default expression of another parameter
Title: Message Title Thomas Hallgren commented on PUP-8728 Re: A parameter that does not pass type validation can cause catalog compilation failure if used in the default _expression_ of another parameter I would have assumed that this already happened but apparently all parameter values are first calculated and then type checked. That's clearly a bug. $test should never be able to hold the value of 63. The fix is probably trivial. The code needs to check each individual parameter instead of checking the full Tuple at the end (probably means that APL assignments must be checked individually as well). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8703) Numeric('0') raises an error
Title: Message Title
Thomas Hallgren commented on PUP-8703
Re: Numeric('0') raises an error
Merged to 5.5.x at 3b737c4.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8603) Move math functions abs, ceil, floor, round, min, max from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8603 Move math functions abs, ceil, floor, round, min, max from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8693) Add a compare() function
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8693 Add a compare() function Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8605) Move sort function from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8605 Move sort function from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8441) Error datatype should support to_json
Title: Message Title Thomas Hallgren commented on PUP-8441 Re: Error datatype should support to_json If all that's needed is a type that describes an array of Result, then why not use Array[Result] and use an alias: type ResultSet = Array[Result] ? That way, it will serialize itself as a plain array of Result objects. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8441) Error datatype should support to_json
Title: Message Title
Thomas Hallgren commented on PUP-8441
Re: Error datatype should support to_json
Alex Dreyer, neither of those JSON examples makes sense to me. The correct output from the Result should be:
{ "__pcore_type__": "Result", "value": , "target": }
A Target should look like this:
{ "__pcore_type__": "Target", "uri": , "options": }
The ResultSet contains results. It should look like this:
{ "__pcore_type__": "ResultSet", "results": }
Add Comment
Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.
Title: Message Title Thomas Hallgren commented on PUP-8500 Re: puppet lookup cli should support adding facts as arguments, not just from a file. I understand that and I'm not in favor of it since it calls for a new option just to cover a corner case. It might also lead to confusion since dotted keys are allowed in the facts file (they need to be quoted when looked up). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title Thomas Hallgren commented on PUP-8606 Re: Module-defined data types are very verbose when displayed This looks like a bug to me. An Object type should represent itself with its name only, not the full spec. The type in the example should present itself as: TargetSpec = Boltlib::TargetSpec = Variant[String[1], Target, Array[Boltlib::TargetSpec]] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8539) Hiera trusted fact lookup
Title: Message Title Thomas Hallgren commented on PUP-8539 Re: Hiera trusted fact lookup Where does "trusted.extension.pp_role" stem from? Does a lookup --compile yield the same result? Some initialization that may affect facts doesn't take place unless a proper compile is performed (ENC initialization is one example). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8441) Error datatype should support to_json
Title: Message Title Thomas Hallgren commented on PUP-8441 Re: Error datatype should support to_json Has the `Bolt::Target` datat type been loaded at the time of the call? If it has, can you please provide a stack trace? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8476) Incorrect handling of white space surrounding comments in EPP
Title: Message Title Thomas Hallgren commented on PUP-8476 Re: Incorrect handling of white space surrounding comments in EPP Merged to master at bf26912. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8476) Incorrect handling of white space surrounding comments in EPP
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8476 Incorrect handling of white space surrounding comments in EPP Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8468) Failed to show puppet classes: 500 Api Request
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8468 Failed to show puppet classes: 500 Api Request Change By: Thomas Hallgren Fix Version/s: PUP 5.5.0 Fix Version/s: PUP 5.5.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8547) MRI and JRuby Yaml parsers not compliant with spec wrt. errors
Title: Message Title Thomas Hallgren commented on PUP-8547 Re: MRI and JRuby Yaml parsers not compliant with spec wrt. errors Andrey Galkin, feel free to suggest what proper YAML parser we could use if you had one in mind. We will need something that uses native code for lex/parse since this is on a performance critical path. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7675) Add the ability to typecast a key using lookup_options
Title: Message Title Thomas Hallgren commented on PUP-7675 Re: Add the ability to typecast a key using lookup_options Merged to 5.5.x at 4dd20f6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8541) Hiera lookup must hard fail on invalid YAML
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8541 Hiera lookup must hard fail on invalid YAML Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8541) Hiera lookup must hard fail on invalid YAML
Title: Message Title Thomas Hallgren commented on PUP-8541 Re: Hiera lookup must hard fail on invalid YAML Duplicates are silently ignored by the Ruby YAML parser although they shouldn't be according to spec: --- somevar: 1 somevar: 2 In Ruby, the last entry wins and a lookup for "somevar" returns the integer 2. Excerpt from the YAML spec: JSON's RFC4627 requires that mappings keys merely “SHOULD” be unique, while YAML insists they “MUST” be. Technically, YAML therefore complies with the JSON spec, choosing to treat duplicates as an error. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You
Jira (PUP-8541) Hiera lookup must hard fail on invalid YAML
Title: Message Title Thomas Hallgren commented on PUP-8541 Re: Hiera lookup must hard fail on invalid YAML While the sample yaml doesn't hard fail, it isn't silently ignored either. The following warning is printed: file does not contain a valid yaml hash" Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8541) Hiera lookup must hard fail on invalid YAML
Title: Message Title Thomas Hallgren commented on PUP-8541 Re: Hiera lookup must hard fail on invalid YAML This is somewhat problematic given that the YAML#load doesn't detect the invalid content. The sample yaml given in the description of this thicket loads ok and produces: ["cls1", "cls2"] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8541) Hiera lookup must hard fail on invalid YAML
Title: Message Title Thomas Hallgren moved an issue Puppet / PUP-8541 Hiera lookup must hard fail on invalid YAML Change By: Thomas Hallgren Affects Version/s: HI 3.4.2 Component/s: PE Component/s: Community Component/s: PE Component/s: Community Key: HI PUP - 597 8541 Project: Hiera Puppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8540) Type checking fails when a sensitive parameter is autoloaded from hiera (no automatic conversion)
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8540 Type checking fails when a sensitive parameter is autoloaded from hiera (no automatic conversion) Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8540) Type checking fails when a sensitive parameter is autoloaded from hiera (no automatic conversion)
Title: Message Title Thomas Hallgren commented on PUP-8540 Re: Type checking fails when a sensitive parameter is autoloaded from hiera (no automatic conversion) I think this will be resolved by Henrik Lindberg's recent work on PUP-7675. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.
Title: Message Title Thomas Hallgren commented on PUP-8500 Re: puppet lookup cli should support adding facts as arguments, not just from a file. That can be achieved by allowing more than one --facts option and then process each file in order and merge their content so that last one wins. Overrides can then be added from the command-line by letting the argument to the last one be a dash. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.
Title: Message Title
Thomas Hallgren commented on PUP-8500
Re: puppet lookup cli should support adding facts as arguments, not just from a file.
An idea, wouldn't it be simpler if we allowed the facts to be read from stdin by using a dash as the name of the facts file? Your command would be similar to:
{code:java}/opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts - --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none <
Jira (PUP-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title Thomas Hallgren commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original Josh Cooper, yes. I think that would be the right thing to do. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8519 Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG
Title: Message Title Thomas Hallgren commented on PUP-8519 Re: Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG Merged to 5.5.x at 5c7279b. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8537) Validator incorrectly reports result of regexp match as being forgotten
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8537 Validator incorrectly reports result of regexp match as being forgotten Issue Type: Bug Assignee: Unassigned Created: 2018/03/08 11:05 PM Priority: Normal Reporter: Thomas Hallgren The following manifest errors when evaluated using puppet apply: 'cdf' =~ /^([a-z])(.*)/ notice($2) The error is: This '=~' _expression_ has no effect. A value was produced and then forgotten (one or more preceding expressions may have the wrong form) This is not correct since the result of the match is stored in numeric variables $1 ... $n and can be used. Turning the comparison into an assignment, i.e.:
Jira (PUP-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG
Title: Message Title
Thomas Hallgren created an issue
Puppet / PUP-8519
Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/03/08 12:43 AM
Priority:
Normal
Reporter:
Thomas Hallgren
Given an _expression_ such as:
@("")
This is heredoc $text
|-END
the lexer attempts to error with Issues::HEREDOC_MISSING_ENDTAG. Since there's no such issue, this instead results in a NameError. The correct issue to use here, given that there's no actual tag, would be Issues::HEREDOC_EMPTY_TAG.
Jira (PUP-8509) move the flatten() function from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8509 move the flatten() function from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8509) move the flatten() function from stdlib to puppet
Title: Message Title Thomas Hallgren commented on PUP-8509 Re: move the flatten() function from stdlib to puppet Merged to master at 2d72551. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8494) Issue based errors are formatted too early and arguments are lost.
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8494 Issue based errors are formatted too early and arguments are lost. Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8494) Issue based errors are formatted too early and arguments are lost.
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-8494 Issue based errors are formatted too early and arguments are lost. Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8510) Enable custom new_function for Object type implementations written in Ruby
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8510 Enable custom new_function for Object type implementations written in Ruby Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8510) Enable custom new_function for Object type implementations written in Ruby
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-8510 Enable custom new_function for Object type implementations written in Ruby Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8510) Enable custom new_function for Object type implementations written in Ruby
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8510 Enable custom new_function for Object type implementations written in Ruby Issue Type: New Feature Assignee: Unassigned Created: 2018/03/05 6:46 AM Priority: Normal Reporter: Thomas Hallgren There's currently no way of writing a custom new_function (the function responsible for creating an instance of a data type) when creating Ruby implementations of an Object data type. Such functions are needed when the default signature generated base on the attributes of the object is insufficient. One example of this is a new_function that accepts repeated parameters where the resulting array is expected to be stored in one attribute, or perhaps split based on type, and stored in several different attributes. Add Comment
Jira (PUP-8508) Add pspec evaluator to Puppet
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8508 Add pspec evaluator to Puppet Issue Type: New Feature Assignee: Unassigned Created: 2018/03/05 6:15 AM Priority: Normal Reporter: Thomas Hallgren Make it possible to run tests writing using the Puppet Specification language (pspec) in the Ruby runtime. This new feature will make it possible to validate the parser, lexer, validator and evaluator in Ruby using the same tests as are used when validating the corresponding functionality in the Go parser/evaluator and in the Java parser/evaluator. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8507) move the join() function from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8507 move the join() function from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8497) move the length() function from stdlib to puppet
Title: Message Title Thomas Hallgren commented on PUP-8497 Re: move the length() function from stdlib to puppet Merged to master at cf57bcd. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8497) move the length() function from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8497 move the length() function from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8502) Puppet lookup always includes classes from the ENC
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-8502 Puppet lookup always includes classes from the ENC Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8502) Puppet lookup always includes classes from the ENC
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8502 Puppet lookup always includes classes from the ENC Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8482) Create a formal representation of the AST that can replace the current dump format
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8482 Create a formal representation of the AST that can replace the current dump format Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8502) Puppet lookup always includes classes from the ENC
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8502 Puppet lookup always includes classes from the ENC Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8502) Puppet lookup always includes classes from the ENC
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8502 Puppet lookup always includes classes from the ENC Change By: Thomas Hallgren Fix Version/s: PUP 4.10.11 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8492) Move the empty() function from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8492 Move the empty() function from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8492) Move the empty() function from stdlib to puppet
Title: Message Title Thomas Hallgren commented on PUP-8492 Re: Move the empty() function from stdlib to puppet Merged to master at 8bbea52. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title Thomas Hallgren commented on PUP-8496 Re: move keys() and values() functions from stdlib to puppet Merged to master at 9804a1b. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8496 move keys() and values() functions from stdlib to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
