client gets json.dumps error trying to serialize datetime objects

[Steve Heyman]

Times are returned as objects in the client. Docs say ISO-8601 formatted strings.

[Douglas Mendizábal (dougmendizabal)]

Docs should be fixed. It's easier to work with time objects in Python. The client should serialize the objects into a string when sending a request to Barbican.

[Steve Heyman (sheyman)]

If that's the way we want to go then this CR (https://review.openstack.org/#/c/155959/) should be abandoned and a new CR written to fix the (currently failing) deserialization of time strings into date objects.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Steve Heyman (<email address hidden>) on branch: master
Review: https://review.openstack.org/155959
Reason: Will change the direction here to use objects rather than strings.

[Steve Heyman (sheyman)]

Renamed this bug to reflect reality.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/156336

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/156336
Committed: https://git.openstack.org/cgit/openstack/python-barbicanclient/commit/?id=2fc4042fd22b2dff35418d599db167366f624a7b
Submitter: Jenkins
Branch: master

commit 2fc4042fd22b2dff35418d599db167366f624a7b
Author: Steve Heyman <email address hidden>
Date: Mon Feb 16 13:05:16 2015 -0600

    Fix serialization of datetime objects

    json.dumps needs a custom default function to handle the
    case of serializing a datetime object with an embedded Utc
    object. This CR adds a generic method to allow anyone
    needed to perform such special processing to include it
    all in one place.

    Change-Id: I84a31e38bf97d83a62108d8cb8f0466ed7fc7d03
    Closes-Bug: 1420442

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-barbicanclient 3.0.3 release.