-
Notifications
You must be signed in to change notification settings - Fork 13
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
Remove indexer management GraphQL API #52
Remove indexer management GraphQL API #52
Conversation
09eef22
to
858e59f
Compare
This API is not supposed to be exposed by the indexer service. It is something that only indexer agent runs to give indexer CLI and other tools the ability to configure the indexer agent behavior.
Among other things, this makes Emacs happy.
858e59f
to
ca15834
Compare
service/src/server/mod.rs
Outdated
@@ -92,12 +88,6 @@ pub async fn create_server( | |||
get(routes::deployment::deployment_health | |||
.layer(AddExtensionLayer::new(slow_ratelimiter()))), | |||
) | |||
.route( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, good catch, I went too far here. 🤦🏻
I'll put the cost model resolver(s) back.
8b704db
to
01dc018
Compare
01dc018
to
db65564
Compare
let pool = &ctx.data_unchecked::<ServerOptions>().indexer_management_db; | ||
indexer_management::cost_model(pool, &deployment).await | ||
} | ||
} | ||
|
||
pub(crate) async fn graphql_handler( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the spirit of remove indexer management graphQL API, perhaps we remove graphql_handler
and use a different handler for the cost
requests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the public cost model API that indexer-service exposes as well — and that is a GraphQL API. So this is correct.
This API is not supposed to be exposed by the indexer service. It is something that only indexer agent runs to give indexer CLI and other tools the ability to configure the indexer agent behavior.