Jira (PUP-5080) Check that no two capability mappings try to set the same parameter

[David Lutterkort (JIRA)]

Title: Message Title

David Lutterkort commented on PUP-5080   Re: Check that no two capability mappings try to set the same parameter In discussions with Ryan Coleman it's actually become clear that we should allow this sort of thing, i.e. that it should be legal to say Foo consumes Bar and Foo consumes Baz where both of them set the same parameter. What should be illegal is consuming both a Bar and a Baz in an instance of Foo: foo {one: consume => Bar[one]} # ok foo {one: consume => Baz[one]} # ok foo { one: consume => [Bar[one], Baz[one]] } # illegal One example of this would be if Bar and Baz were capabilities for different sorts of RDBMS - essentially, we'd do some variation of variant types here. Add Comment   This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.