Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Josh Cooper commented on PUP-6453 Re: Produced capabilities are evaluated before the component produces/consumes is deprecated and will be removed, closing 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-6453) Produced capabilities are evaluated before the component
Title: Message Title Moses Mendoza commented on PUP-6453 Re: Produced capabilities are evaluated before the component Alex Dreyer is this still an issue? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6453) Produced capabilities are evaluated before the component
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Moses Mendoza Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6453) Produced capabilities are evaluated before the component
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Moses Mendoza Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6453) Produced capabilities are evaluated before the component
Title: Message Title Nick Lewis assigned an issue to Unassigned Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6453) Produced capabilities are evaluated before the component
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer commented on PUP-6453 Re: Produced capabilities are evaluated before the component Using puppet lookup and module data this issue can be worked around as long as you only set those values through puppet lookup. I have an example in a pr against the wordpress_app module Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Alex Dreyer Sprint: bugs under investigation Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Alex Dreyer Sprint: bugs under investigation Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer commented on PUP-6453 Re: Produced capabilities are evaluated before the component That is true. We have to decide whether we want produce statements to be based purely on facts, and external data/classification. If that is the case we should move produce evaluation before any class is evaluated. Right now the behavior is inconsistent since the included class may or may not have been evaluated first. Give the natural semantics of 'produce' it's also counter-intuitive and leads to unexpected bugs when moving components around. The problem that led me to this is a data problem not that I really need the class evaluated. Let me see if I can solve it with lookup. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title David Lutterkort commented on PUP-6453 Re: Produced capabilities are evaluated before the component If I understand this right though it would require that the underlying component gets evaluated before we can evaluate the produced resource, right ? IOW, it would make it impossible to evaluate produced resources when we compile the environment catalog without compiling a good part of the node catalogs, too ? That seems like a significant change to me that we won't be able to ever undo and we need to make sure that we are ok with committing to that mode of compilation. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer commented on PUP-6453 Re: Produced capabilities are evaluated before the component This PR wont' work because of this issue: https://github.com/puppetlabs/puppetlabs-wordpress_app/pull/2 The issue is on: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/resource/type.rb#L173 When we are evaluating the component we evaluate the produced capability first. Therefore any variables that are assigned during the components evaluation are not available to use in the produce mapping Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title David Lutterkort commented on PUP-6453 Re: Produced capabilities are evaluated before the component I can't claim to fully understand the issue here - logically, it makes sense to evaluate produced capres after the component that produces them. We should make sure though that we keep the option to evaluate capres while evaluating the environment catalog, i.e. that it is possible to do this evalation without evaluating the underlying resource. Is there some code that clarifies the problem ? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Ryan Coleman commented on PUP-6453 Re: Produced capabilities are evaluated before the component Ping David Lutterkort just for visibility. I'm good with this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer created an issue Puppet / PUP-6453 Produced capabilities are evaluated before the component Issue Type: Bug Assignee: Unassigned Created: 2016/06/28 4:57 PM Priority: Normal Reporter: Alex Dreyer We evaluate the produced capabilities of a component before that component is evaluated. That means if a reusable database component includes a shared class to configure the underlying database it can't use params on the included class in it's produce statements. To fix this the produces should be evaluated after the rest of the component. If we want to keep internal scope from the component from leaking through this will require a new scope. Add Comment This message was sent by Atlassian JIRA (v6.4.13
