-
Notifications
You must be signed in to change notification settings - Fork 252
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
feat: expose config using an API #2817
Comments
/bounty $200 |
💎 $200 bounty • Tailcall Inc.Steps to solve:
🙏 Thank you for contributing to tailcallhq/tailcall!
|
/attempt #2817
|
@ssddOnTop: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
is there a reason to generate a |
The bounty is up for grabs! Everyone is welcome to |
Does the provided mutation update the configuration when the Tailcall service is online?
|
/attempt #2817
|
@karatakis: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
The bounty is up for grabs! Everyone is welcome to |
/attempt #2817 Options |
closing this one in favour of #2903 |
@EveEdwin: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
The bounty is up for grabs! Everyone is welcome to |
Action required: Issue inactive for 30 days. |
Create a new route
/graphql
which internally exposes a GraphQL API with the following schemaTechnical Requirements
server.admin.port
settingThe text was updated successfully, but these errors were encountered: