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

Use TypeIndexes in addition to VOID endpoint #1255

Open
srosset81 opened this issue May 22, 2024 · 0 comments
Open

Use TypeIndexes in addition to VOID endpoint #1255

srosset81 opened this issue May 22, 2024 · 0 comments
Milestone

Comments

@srosset81
Copy link
Contributor

srosset81 commented May 22, 2024

"Classical" SemApps instances have the possibility to deploy a VOID endpoint, which is used then by the data provider to find the containers based on the type of resources being requested.

On a Pod provider config, we cannot use a VOID endpoint because it would depend on each Pod. VOID endpoints use /.well-known URLs, and so we can have only one per domain name. As a consequence, we need to hard-code on the data provider config the containers that are available.

However, as soon as Pods supports TypeIndexes, we can use them instead of VOID to find the available containers.

Of course VOID should still be used when available.

@srosset81 srosset81 changed the title Use TypeIndex instead of VOID endpoint Use TypeIndex in addition to VOID endpoint May 22, 2024
@srosset81 srosset81 changed the title Use TypeIndex in addition to VOID endpoint Use TypeIndexes in addition to VOID endpoint May 22, 2024
@srosset81 srosset81 added this to the Version 2.0 milestone Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant