Fix issue "redis" engine is not registered#19239
Conversation
smallinsky
left a comment
There was a problem hiding this comment.
Does the init call was for redis engine in previous version was called from https://github.com/gravitational/teleport/pull/18776/files#diff-054e31280a78f4aea4759cd740f8d8bcecf563679d7fe6b79991fdb944e8c611L64 ?
LGTM to me though I think that we should clean when and how our db engines are registered to prevent this to happen again.
Yes. We were calling
Agreed. The test didn't catch the problem as the test has to import redis for other setups. Need to ensure this won't happen again. How about checking if every engine type is registered at server start(or New)? |
Yes that will work but I wonder if we can be more explict and insteam of calling and makes things more readable. |
@smallinsky really like that. Will do that separately. The test registers fake engine in |
Error when connecting Redis database
Related PR
(interestingly, this is not caught by test, likely because test has different importing path)