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|internal|admin…other] [url] [enabled] [is_global]

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
Completed by
Joseph Heck

Related branches

Sprints

Whiteboard

I suggest handling it in this way.
Denormalize endpoint templates all together.Introduce a new model called
endpointTemplateURLs which have a one to many relationship between endpointTemplates.

endpointTemplateURLs

id
endpointTemplate_id
endpointTemplateURLType => (could be public,admin,internal or more)
is_client_visible => (If set to true would be shown to the client ie service api calls)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.