Add put functionality to Oauth2 Client

[kylevillegas93]

Description

• This change adds a put function to the Oauth2Client
• I want to use this client with XML, thus I am not coupling this method to json.

Testing

make unit

[nonword]

Ideally the put method wouldn't have a different signature than the other method sigs. In order to support sending non-json payloads (which I assume you intend to do via kwargs['data']?), we have some options to consider:

• Implement put using standard signature (i.e. put(self, request_path, json, **kwargs) and your integration may be able to just pass None as second arg? The client would still be json-inclined, but support this as a workaround for sending non-json payloads
• Or we change the standard signature declaring json as a required second arg in patch and post, obligating integrations to pass it in kwargs. This would be a breaking change.
  Thoughts, @charmingduchess ?

[sarangj]

I was thinkin something similar, but it's also not completely clear to me what the scope / purpose of this class is. It's named like a generic oauth2 client, but it seems to have some platform api specific implementation details / functionality.

[nonword]

Yeah naming things is hard. We would have called it PlatformApiClient, but we also use it for interacting with Sierra, which makes similar auth and payload choices. The uniting theme (and only real convenience provided by use of this client) is it does the oauth2 auth for you - hence the name.

[kylevillegas93]

Makes sense - I'm aligned with keeping the method signatures the same and maybe we can revisit changing the standard signature later on?

[charmingduchess]

Yea I was going to say the same thing. I think the signatures should match. Maybe for a major release we can reconsider the favoring of json. But for now let's keep the signatures the same.