{"push_id":601566028,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"3693ea2a63780e5ab792fcb14d0f4e73a6d8150d","before":"456ec16fd2d1dc82b78d58ef6f4144dd68ed7475","commits":[{"sha":"46ef634de8c6867fa0d18fb4c3618cfca8516038","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@doug.gt","name":"Douglas Mendizábal"},"message":"Deprecate setting the payload type and encoding\n\nDeprecate manually setting the payload_content_type and\npayload_content_encoding properties of a secret.  With this CR a user of\nthe client only needs to provide the payload, and the client will figure\nout what the correct payload_content_type and payload_content_encoding\nvalues should be.\n\nSetting these properties for the user lets us avoid a lot of weird\nbehaviors such as the one described in Bug #1419166, and also lets us\navoid errors that happen when a user mismatches the payload and an\nincorrect content type.\n\nIn the interest of backwards compatibility, these properties are still\nusable, but will log deprecation warnings.  They should be removed in a\nfuture version after current users have had enough time to update their\ncode bases.\n\nChange-Id: Ibfe3ad42e11bd83c002d0f1b69fb8a323a7b6f3d\nCloses-Bug: #1419166","distinct":true,"url":"https://api.github.com/repos/cloudkeep/python-barbicanclient/commits/46ef634de8c6867fa0d18fb4c3618cfca8516038"},{"sha":"3693ea2a63780e5ab792fcb14d0f4e73a6d8150d","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Deprecate setting the payload type and encoding\"","distinct":true,"url":"https://api.github.com/repos/cloudkeep/python-barbicanclient/commits/3693ea2a63780e5ab792fcb14d0f4e73a6d8150d"}]}