424a633fd9
The Neutron 'created_at'/'updated_at' fields on API resources were inconsistent with other OpenStack projects because we did not include timezone information. This patch addressed that problem by adding the zulu time indicator onto the end of the fields. Because this could break clients expecting no timezone, this patch also eliminates the 'timestamp_core' and 'timestamp_ext' extensions and consolidates them into a new 'timestamp' extension. This makes the change discoverable via the API. This is assuming the current API development paradigm where extensions can come and go depending on the deployment and the client is expected to handle this by checking the loaded extensions. Once we decide extensions are permanent, this type of change will no longer be possible. Even though this is being proposed late in the cycle, it is better to get this change in before the release where we expose even more resources with incorrectly formatted timestamps. APIImpact Closes-Bug: #1561200 Change-Id: I2ee2ed4c713d88345adc55b022feb95653eec663
17 lines
723 B
YAML
17 lines
723 B
YAML
---
|
|
prelude: >
|
|
- The created_at and updated_at fields available on Neutron
|
|
resources now include a timezone indicator at the end.
|
|
Because this is a change in format, the old 'timestamp_core'
|
|
extension has been removed and replaced with a 'timestamp'
|
|
extension.
|
|
upgrade:
|
|
- The 'timestamp_core' extension has been removed and replaced
|
|
with the 'standard-attr-timestamp' extension. Objects will still
|
|
have timestamps in the 'created_at' and 'updated_at' fields, but
|
|
they will have the timestamp appended to the end of them
|
|
to be consistent with other OpenStack projects.
|
|
fixes:
|
|
- Bug 1561200 has been fixed by including the timezone with
|
|
Neutron 'created_at' and 'updated_at' fields.
|