<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 9, 2014 at 9:00 PM, Brian Stansberry <span dir="ltr"><<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":3uy" class="a3s" style="overflow:hidden">5) Why would I use an attribute group instead of a child resource?<br>
<br>
Because requiring users to add a child resource just to set a bunch of<br>
values that are really part of the config of the parent resource forces<br>
them to use a CLI batch to correctly configure the parent resource.</div></blockquote></div><br><br></div><div class="gmail_extra">One thing that I am not sure about this is, how do we do validation for things like this?<br><br></div><div class="gmail_extra">Simple example would be "required" validation for attribute group.<br></div><div class="gmail_extra">You want to enforce few attributes that are part of the group to be required.<br><br>but on other hand you don't want to enforce them as part of resource:add operation.<br>as they are only "required" when you are editing / adding attribute group.<br><br></div><div class="gmail_extra">With current code we enforce required for all attributes on a resource that is being added.<br></div><div class="gmail_extra">Which is bit inconvenient for when we have attribute groups and want to do it bit differently.<br><br></div><div class="gmail_extra">So question is should we support selective validation based on groups or not?<br></div><div class="gmail_extra"><br><br></div><div class="gmail_extra">--<br></div><div class="gmail_extra">tomaz<br></div><div class="gmail_extra"><br></div></div>