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

Explicit export #145

Open
bartoszmajsak opened this issue Jan 20, 2025 · 1 comment
Open

Explicit export #145

bartoszmajsak opened this issue Jan 20, 2025 · 1 comment

Comments

@bartoszmajsak
Copy link
Collaborator

Allow users to explicitly define specific services for export by listing them in a format as <namespace>/<service>.

This gives the admin full control over exported services.

Example structure

serviceList:
  - "ns-1/ratings"
  - "ns-1/reviews"
  - "ns-2/*"
@bartoszmajsak
Copy link
Collaborator Author

Similar to #144, we should carefully consider the exact use cases. One aspect that isn't clear to me is how we should handle cases where e.g. ns-2 is not part of the mesh. It's important to explicitly define this behavior and document it accordingly.

I think the general assumption is that we only consider namespaces which are part of the mesh, but we need to be clear on it to avoid ambiguity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant