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

Allow public boundaries #84

Open
gmac opened this issue Nov 1, 2021 · 1 comment
Open

Allow public boundaries #84

gmac opened this issue Nov 1, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@gmac
Copy link
Contributor

gmac commented Nov 1, 2021

@nmaquet something for the v2 roadmap: I think the strategy of hiding boundary queries from the gateway schema is a good default, however it thwarts dog-fooding when there’s a query method explicitly intended to perform double-duty for both public and gateway traffic. This is particularly important when federating with locked API releases that forbid schema changes.

My suggestion would be to include an option for boundary accessors that opts them into the public schema. Conflicting public accessors would simply fail validation.

@nmaquet
Copy link
Contributor

nmaquet commented Nov 1, 2021

Happy to consider this for 2.0, thanks.

@nmaquet nmaquet added the enhancement New feature or request label Nov 1, 2021
@nmaquet nmaquet modified the milestone: Bramble 2.0 Nov 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants