{"push_id":857426773,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"f71c7a732e5c376bf496ba0597099d19d5e9d40f","before":"d0b2b5554012ea76c0ef88ad268effe7e938b292","commits":[{"sha":"bd977f400a1192d5cf7c2b52ef91615c0828813c","author":{"email":"2c1c04960e5094d519e914b7f827193df42cff08@us.ibm.com","name":"Matt Riedemann"},"message":"Add SensitiveString field type\n\nThere are objects that define a String field to hold a serialized json\nblob and that blob can have sensitive information in it (tokens,\npasswords, etc). When the object is logged, repr will log that sensitive\ninformation. This puts a burden on the code that's doing the logging to\nremember to sanitize the object's string form before logging it.\n\nIt'd be simpler and cleaner to just have a field type that extends\nString so it's the same in all respects except for when it's\nstringified. So in SensitiveString's stringify method it just masks the\npassword on the field value before returning it.\n\nAnd no SensitiveString does not play an acoustic guitar at your local\ncoffee shop, he's actually super tough and emotionally walled up, that's\nwhy he doesn't like exposing too much information about himself in the\nlogs.\n\nCloses-Bug: #1321785\n\nChange-Id: I56466eb8b5d8000ef010f2015f453a9e74dc66b8","distinct":true,"url":"https://api.github.com/repos/openstack/oslo.versionedobjects/commits/bd977f400a1192d5cf7c2b52ef91615c0828813c"},{"sha":"f71c7a732e5c376bf496ba0597099d19d5e9d40f","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Add SensitiveString field type\"","distinct":true,"url":"https://api.github.com/repos/openstack/oslo.versionedobjects/commits/f71c7a732e5c376bf496ba0597099d19d5e9d40f"}]}