As an administrator I do not need to see the resulting data from add and mod commands. Add an option to skip the retrieval of the created entry and the post_callback() calls which may massage it. Return no data to the client beyond success/failure.
For example, on a successful user-add this would be returned with --quiet:
{ "error": null, "id": 0, "principal": "admin@EXAMPLE.TEST", "result": { "result": {}, "value": "" }, "version": "4.x.x" }
This is interesting for automation and bulk imports that don't care about the specifics of an operation and just want to know if it failed.
This also suppresses at least one LDAP search.
Metadata Update from @rcritten: - Issue assigned to rcritten
add/remove members is not a candidate for --quiet because of add_external_post_callback() which may do an LDAP update.
My quest has hit a bit of a snag. A few plugins were using post_callback() for real work but typically they were easy to fix by moving those things to execute instead.
dns is another matter. It is hugely complex and does this in a number of places. I'm not sure the impact if I start moving that code around.
My goal was to enable quiet globally for add/mod. It may be safer to enable it in discrete plugins at least initially. It may require a bit of duplication though, we'll see.
I have the xmlrpc tests already aware of quiet and may leave it possible in all plugins but it just will never fire for those that may never end up with a quiet option.
Login to comment on this ticket.