Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references I should have removed the mention of meta parameters completely - the more general rule covers them. These two parts still make it sound like defined resource types are handled differently, and that their default values in the parameter list have some effect, which I showed isn't true. You showed that an unevaluated resource does not have values (resource creation is lazy, your notice happens before the user defined resource's body is evaluated). The spec should point that out. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg assigned an issue to Nicholas Fagerlund Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Henrik Lindberg Assignee: HenrikLindberg NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references Specification updated. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title
Henrik Lindberg commented on PUP-4513
Re: Language spec does not document behavior of access operator on resource references
i.e. this works: define foo($bar=20) { notice bar is $bar }
define display { notify {y: message = foo[bar] = $ {Foo[x][bar]}
} } foo {x: }
display {y: }
Due to the lazy evaluation, it is not enough to follow the instantiation with a notice or notify (native types are not lazily evaluated), it must be done inside of a resource that is evaluated later.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references Lookup of a parameter that at the time of accessing it has no value depends on if the resource type is a user defined or not, and if the attribute is a meta parameter, or if the value That still makes it sound like metaparameters are handled differently. Lookup of a parameter that at the time of accessing it has no value depends on _if the resource type is a user defined or not,_ and if the attribute is a meta parameter, or if the value ... If a parameter is not explicitly set, a default value is returned if a user defined type's parameter has a default value _expression_, or... These two parts still make it sound like defined resource types are handled differently, and that their default values in the parameter list have some effect, which I showed isn't true. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund assigned an issue to Henrik Lindberg Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Nicholas Fagerlund Assignee: NicholasFagerlund HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund assigned an issue to Henrik Lindberg Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Nicholas Fagerlund Assignee: NicholasFagerlund HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references If a parameter is not explicitly set, a default value is returned if a user defined type's parameter has a default value _expression_, or if there is a Resource Defaults _expression_ that defines a default value. Henrik Lindberg The first part, about defined resource types, is wrong. Demonstration here. The second part is right, but the spec should mention that THAT's evaluation-order dependent as well, since resource default statements usually ignore evaluation order. The part about metaparameters is unclear. You state that they behave differently, but your description of the behavior sounds like how other attributes work (i.e. only an explicitly set value can be accessed). What's actually different? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4513
Language spec does not document behavior of access operator on resource references
Change By:
Henrik Lindberg
The[sectionontheaccessoperator|https://github.com/puppetlabs/puppet-specifications/blob/master/language/expressions.md#--access-operator]alludestoitsuseonresourcereferences,butthereisn'tapeersubsectiononresourcereferencestogoalongwiththearray/string/hashsections.[Thisfileinevilmademanifest|https://github.com/nfagerlund/evil-made-manifest/blob/master/future_resource_attribute_access.pp]showsmostofthetrickybitsthatthespecdoesn'tcover.TheremayalsobesubtletiesIdon'tknowaboutyet. UPDATE---Thissection:https://github.com/puppetlabs/puppet-specifications/blob/master/language/expressions.md#resource-type--describesthevariouswaysthe{{\[]}}operatorappliestoaResourcetype-theabilitytogetattributesaredescribedlastinthatsection.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg assigned an issue to Nicholas Fagerlund Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Henrik Lindberg Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4513
Language spec does not document behavior of access operator on resource references
Change By:
Henrik Lindberg
The[sectionontheaccessoperator|https://github.com/puppetlabs/puppet-specifications/blob/master/language/expressions.md#--access-operator]alludestoitsuseonresourcereferences,butthereisn'tapeersubsectiononresourcereferencestogoalongwiththearray/string/hashsections.[Thisfileinevilmademanifest|https://github.com/nfagerlund/evil-made-manifest/blob/master/future_resource_attribute_access.pp]showsmostofthetrickybitsthatthespecdoesn'tcover.TheremayalsobesubtletiesIdon'tknowaboutyet.UPDATE---Thissection:https://github.com/puppetlabs/puppet-specifications/blob/master/language/expressions.md#resource-type--describesthevariouswaysthe{{\[]}}operatorappliestoaResourcetype-theabilitytogetattributesaredescribedlastinthatsection. Thatsectioninthespecificationhasnowalsobeenupdatedtoalsoincludecasesthatleadstoanerroranditdetailstherulesforparameterswithoutvalues,metaparameters,andwhenadefaultvalueisproduced.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references Specification reviewed and updated. The description in this ticket is also updated. Nicholas Fagerlund can you review? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references Will update spec wrt. Resource Default expressions being evaluation order dependent. It is true that meta parameters can only be accessed if explicitly set. The fact that they may have default values, and that those may be derived/computed from other values set etc. is besides the point, those values are set very late and cannot be accessed. Will update the spec. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg assigned an issue to Nicholas Fagerlund Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Henrik Lindberg Assignee: HenrikLindberg NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references Spec updated. Better now? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Steve Barlow Sprint: Language2015-05-13 ,Language2015-05-27 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Kurt Wall QA Risk Assessment Reason: Noassessmentneededforlanguagespecchanges Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Kurt Wall QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Change By: Henrik Lindberg Sprint: Language2015-05-13 Scrum Team: Language Story Points: 1 Scope Change Reason: docs/spec-forrelease,mustbedone Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references Will review and make sure it is reflected in the specification. Getting attributes from resources depends on the order of evaluation - it is not possible to get values set via Resource defaults, nor to get values of meta parameters (since these are set after user code has stopped evaluating; i.e. blanks are filled in by the compiler at the end using collectors with overrides and attributes set at the resource type level (Resource Default Expressions). The example in evil made manifests show exactly that. It may very well be that the spec is vague in this area because we did not fully understand what was actually possible in various situations. And we discussed for a long time if we should try to formalize behavior that is driven by the compiler as opposed the language - you will find the spec vague in several areas that deal with resources, collectors, overrides, defaults and meta parameters (or it may say that the behavior is undefined). I will review the parts of the spec that relate to this and make it clearer. Not certain what we want the specification to say; simply that it is evaluation order dependent (you have to know how the evaluator and compiler does it), or if it should specify how the compiler does this now (which is perhaps not how we really want it to work, and to be honest, we really don't know all the corner cases), or state that it is undefined? We may want the documentation to say something different like you can only read attributes that are explicitly set. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Issue Type: Task Assignee: Unassigned Components: Language Created: 2015/05/01 11:06 AM Labels: specification Priority: Normal Reporter: Nicholas Fagerlund The section on the access operator alludes to its use on resource references, but there isn't a peer subsection on resource references to go along with the array/string/hash sections. This file in evil made manifest shows most of the tricky bits that the spec doesn't cover. There may also be subtleties I don't know about yet. Add Comment
