Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EDS API: Application Endpoints functionality to be a new API #286

Open
javierlozallu opened this issue Jul 22, 2024 · 0 comments
Open

EDS API: Application Endpoints functionality to be a new API #286

javierlozallu opened this issue Jul 22, 2024 · 0 comments
Labels
correction Suggesting corrections of API specification or indicating misalignment with API design guidelines

Comments

@javierlozallu
Copy link
Collaborator

Problem description
This Operation allows to: Register and manage the routable Application Endpoints of your deployed applications.
Currently the approach is that endpoints are fully managed by the Edge Platform and Developers can ask for this information through GET /apps/{appId}/instances EAM API method.
I don't found any intent related to this capability but I think is very interesting to have it because of two reasons:

  • If the developer deploys the application on a hyperscaler
    
  • If the developer wants to use their own domains, this relates to a comment in 
    

Shouldn't the AccessEndpoints also contain the protocol #271 to have a new API: Bring Your Own DNS/Endpoint/Whatever which allows the developer to use and manage third party domains (other than the Edge platform). So this contribution will serve as a basis for this.
A different approach I see here is to add it in the onboarding process within the EAM API, but I don't quite like it.

Expected behavior
Create separate yaml for Application end point registry. This is more edge cloud specific but still reusable across the sub projects.

@javierlozallu javierlozallu added the correction Suggesting corrections of API specification or indicating misalignment with API design guidelines label Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correction Suggesting corrections of API specification or indicating misalignment with API design guidelines
Projects
None yet
Development

No branches or pull requests

1 participant