support project property unset in identity v3

[Rui Chen]

We can set and update the properties of project, but can't unset the existed properties of project object in identity v3(identity v2 support unset). OSC should support it in order to remove the property that we don't need.

[wangxiyuan (wangxiyuan)]

keystone client droped the null values in v3: https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/base.py#L399

So using keystone client, we can't set the project's property to null in v3 now. But it works when sending "null" value to keystone server side with the REST request.

I think we should fix the keystone client issue first.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by wangxiyuan (<email address hidden>) on branch: master
Review: https://review.openstack.org/296246

[OpenStack Infra (hudson-openstack)]

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

[Lance Bragstad (lbragstad)]

Unassigning due to inactivity. If someone has the bandwidth to pick up the proposed patch and push it forward, please feel free to do so.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Morgan Fainberg (<email address hidden>) on branch: master
Review: https://review.openstack.org/375239
Reason: administratively abandoning this patch. It can be restored if someone is going to pick it up.

[Morgan Fainberg (mdrnstm)]

Generally speaking there should be no use of extras in Keystone. This fix should be incorporated into SDK as it is not likely KSC will be maintained (new fuctionality/non-security fixes) much beyond SDK getting a 1.0 release

[Dejan SANADER (d-sanader)]

Hello,

The API and the CLI still allow adding properties to project, but neither allow removing them.

If it's a deprecated feature, why just not disallowing additional properties in the project schema ?