Create Endpoint Identifiers
Endpoints may change (the version may change, the region may get renamed, the URL could change as well). A client may want to keep track of which endpoint a resource is in. To do that, they need an identifier for that endpoint that they know won't change. Maybe use portable IDs: https:/
No API spec changes needed. The spec supports an ID already.
Keystone Implementation: Since each Endpoint in the Keystone is generated by an endpoint template, and each template generates one endpoint. The endpoint template ID may be used to address this blueprint. While the ID won't be unique to distinguish endpoints between tenants, it will server the intent of this blueprint, allowing clients to identify a particular endpoint when attributes change.
Blueprint information
- Status:
- Complete
- Approver:
- Ziad Sawalha
- Priority:
- Medium
- Drafter:
- Ziad Sawalha
- Direction:
- Approved
- Assignee:
- Ziad Sawalha
- Definition:
- New
- Series goal:
- Accepted for essex
- Implementation:
-
Implemented
- Milestone target:
-
2012.1
- Started by
- Ziad Sawalha
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Return Endpoint IDs
Work Items
Dependency tree
* Blueprints in grey have been implemented.
