<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 10, 2014 at 3:45 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=":1iq" class="a3s" style="overflow:hidden">This sounds more like a complex attribute or a child resource. The attributes control a discrete piece of functionality and<br>
you need to be able to turn that on/off as a unit. The attributes are required if that functionality is turned on.</div></blockquote></div><br></div><div class="gmail_extra">Agreed, but how do you handle scenario where you just add resource that has 30 attributes all in attribute groups.<br></div><div class="gmail_extra">You call :add() without any parameters as you plan to add/edit attributes that are part of attribute group in next step.<br></div><div class="gmail_extra">you than call :write-attribute(name=non-require-attribute-that-is-part-of-group-that-has-few-required, value="some-value")<br>and this should fail, as attribute is part of attribute group.<br><br></div><div class="gmail_extra">It is a tricky thing to address, as we have not atomic way to write/update more than one attribute at ones.<br></div><div class="gmail_extra">maybe have extra operation to do write-attribute-group(name="first-attribute-group", attr1=value,attr2=value) similar to :add semantics.<br><br>otherwise I don't see any good way to do atomic updates of whole attribute group.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><br><br></div></div>