yahoo-eng-team team mailing list archive

[Morgan Fainberg <morgan.fainberg@xxxxxxxxx>]

This is actually not a bug, but the intended mechanism. All extra values
are handled as part of the returned object (at the top level). They are
only stored in backing store as a JSON blob. The intention is that if
you add the 'test' attribute to your tenant it would be returned at the
top as <tenant_object>.test

The example you provided as the expected result would not work as there is no way to reference the 'extra' fields, it would need to be:
{
            "description": null,
            "enabled": true,
            "id": "dc0a88dc51624167b747211ec050a08e",
            "extra": {
                   "test": "value"
             },
            "name": "admin"
}

This would be an incompatible API change for both v2.0 and v3.

** Changed in: keystone
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1346201

Title:
  v2.0/tenants fails to report the 'extra' field values in the project

Status in OpenStack Identity (Keystone):
  Invalid

Bug description:
  Assume that, the project "admin" is created in the keystone db with
  "extra" filed having following values:

  {"test":"value"}

  Then on running GET on the REST API v2.0/tenants, returns the
  following response

  {
              "description": null,
              "enabled": true,
              "id": "dc0a88dc51624167b747211ec050a08e",
              "test": "value", <<<< ---------- ERROR
              "name": "admin"
  }

  This should be returning the response as follows:

  {
              "description": null,
              "enabled": true,
              "id": "dc0a88dc51624167b747211ec050a08e",
              {
                     "test": "value"
              },  <<<<<<<<< -- JSON String
              "name": "admin"
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1346201/+subscriptions