Flatten Endpoint Templates using Endpoint Types
Registered by
Ziad Sawalha
Instead of having hard-defined publicURL, adminURL, and internalURL, instead have one URL and an EndpointType. That would allow us to do this:
endpointTemplate add [region] [service] [type=public|
That would allow services to register as many endpoints and endpoint types as they needed.
Blueprint information
- Status:
- Complete
- Approver:
- Ziad Sawalha
- Priority:
- Undefined
- Drafter:
- Ziad Sawalha
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Joseph Heck
Related branches
Related bugs
Sprints
Whiteboard
I suggest handling it in this way.
Denormalize endpoint templates all together.Introduce a new model called
endpointTemplat
endpointTemplat
id
endpointTemplate_id
endpointTemplat
is_client_visible => (If set to true would be shown to the client ie service api calls)
(?)