Jason Frey
Jason Frey
As discussed, in my opinion this should already be possible since it's an attribute and attributes can be modified via PUT/PATCH
I think this can technically be done now by setting the role value in settings (via the settings api on a server), but that is admittedly weird
I think my issue is that we have no way of paging those associations even if we did add a limit, and then we also have no way of telling...
> My thinking is that the problem stems from users not knowing they are making poor choices with the API I agree, but I can't see anything we can do...
> > Maybe an option is to have a blacklist of associations that we know can tend to be large (vms, events, notificatioons, etc), and only apply the new logic...
It's possible that's not exposed via the API, as those provisioning forms are some of the oldest in the app (from before we even had an API). I'm going to...
@kbrock Do you know if we have this?
Some of this is already found in open issues... I'll associate them around. Also I thought service catalogs had a endpoint, but I'll have to search.
When this gets worked on we have to make sure we distinguish current group from "all groups. I wonder if this just needs subcollection support.
@kbrock Can you add some comments here on what you've found.