feat: lazy load and hot reload for policies#890
feat: lazy load and hot reload for policies#890XVincentX merged 17 commits intoExpressGateway:masterfrom
Conversation
8c92276 to
038d5ab
Compare
9de54d9 to
d05f51d
Compare
Codecov Report
@@ Coverage Diff @@
## master #890 +/- ##
==========================================
+ Coverage 88.82% 89.08% +0.26%
==========================================
Files 136 137 +1
Lines 3695 3711 +16
==========================================
+ Hits 3282 3306 +24
+ Misses 413 405 -8
Continue to review full report at Codecov.
|
XVincentX
left a comment
There was a problem hiding this comment.
Good start.
I'd like to get a clarification on why you needed to load some policies in the tests although these are not used.
Another thing that needs to be verified is whether, by making an hot reload with a new policy, it gets loaded correctly and does not make the gateway crash.
Having a test checking this functionality would be great!
Good work though!
d9a7249 to
de38388
Compare
121d6f3 to
598f5be
Compare
- only load policies defined in the gateway config fixes ExpressGateway#870
- add hot reload for policy changes in config file - earlier, policies were not relaoded on hot reload
598f5be to
c30f31d
Compare
XVincentX
left a comment
There was a problem hiding this comment.
This looks promising, I can definitely see some progress. I've left another round of comments and I'm right now looking into the tests to figure out and fix the issue you were facing.
6b88ea8 to
831cd98
Compare
|
@XVincentX Do we also need to remove policies which are removed from the config on hot reload? |
|
@ravikp7 No; they're on memory already so it does not make sense to unload them. In any case I took care of it and I'm adding an e2e test. See the code in case you're interested! |
feat: lazy load and hot reload for policies
fixes #870