GIve up artificial primary keys in creation queries
Registered by
Alexej Ababilov
According to Keystone Developer Guide, artificial primary keys must be given in queries while adding a role to user, endpoint to tenant, and so on.
For example, to add a role to user, we must provide something like:
{
"roleRef":{
"id":1,
"roleId":"admin",
"tenantId":"one"
}
"id" is an artificial primary key. In fact, it is autogenerated. So, documentation should be updated.
Blueprint information
- Status:
- Complete
- Approver:
- Ziad Sawalha
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Yogeshwar
- Definition:
- Approved
- Series goal:
- Accepted for diablo
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Ziad Sawalha
- Completed by
- Ziad Sawalha
Related branches
Related bugs
Sprints
Whiteboard
ZNS 2011-10-21: Agreed.
Yogi: We no more use role refs.The calls have changed.Should be closed as it is no longer applicable.
(?)