IMO, I don't think it's necessary to pollute the Change Log with Delivery Service Requests (DSRs) comments. I think DSRs are turning out to be the Change Log for Delivery Services and comments on those are Change Log noise.
-Dew On Wed, Mar 21, 2018 at 10:24 AM, Jeremy Mitchell <[email protected]> wrote: > Currently, every POST (create), PUT (update) or DELETE (delete) TO API > endpoint (or most of them) create a change log entry. > > For example when i PUT /api/cachegroups/4 it creates this CL entry: > > myusername - Updated Cachegroup named 'Foo' with id: 57 > > Question: In the golang rewrite of the TO API should EVERY POST, PUT > and DELETE trigger a change log entry? Or should it be optional and > determine by the developer? > > I ask because I'm adding endpoints for create, update and delete of > delivery service request comments and it feels like too much to create a > change log entry for that. I'd hate to pollute the change log for minor > stuff. > > To me, it seems like it should be optional and determined by the API > developer. > > Jeremy >
