-
Notifications
You must be signed in to change notification settings - Fork 135
WIP add application scopes framework and healthscope #160
Conversation
7c6f4a0
to
80cd339
Compare
80cd339
to
8c1c0c0
Compare
8c1c0c0
to
e981227
Compare
7204283
to
001bc53
Compare
40b0a9b
to
3010f9a
Compare
@technosophos I find this PR could be very large, will it hard to review? |
3010f9a
to
5cb54e4
Compare
02a80d1
to
a63e9c0
Compare
healthscope/src/main.rs
Outdated
health_scope_watch.join().unwrap() | ||
} | ||
|
||
//FIXME: Error(BlockingClientInFutureContext) https://github.com/clux/kube-rs/issues/63 |
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.
Now we can't get health status response, because the client we invoke didn't implement async. kube-rs/kube#63
It will occur Error(BlockingClientInFutureContext)
when we invoke synchronize function in hyper
here .
I've tried several ways to work around, they don't work. Could someone more familiar with rust web framework than me give some help?
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.
I have fixed this
b81c95d
to
1f4dfa6
Compare
I am holding this PR back until after 1.0.0-alpha.1. |
closing this, we move to #367 |
This PR is mainly to add application scope framework and health scope
This PR lasts several weeks mostly because the spec is changing.
https://github.com/microsoft/hydra-spec/issues/130
https://github.com/microsoft/hydra-spec/issues/144
https://github.com/microsoft/hydra-spec/pull/133
https://github.com/microsoft/hydra-spec/pull/127
https://github.com/microsoft/hydra-spec/pull/177
https://github.com/microsoft/hydra-spec/pull/196
add application scopes framework
add health scope