-
Notifications
You must be signed in to change notification settings - Fork 10
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
Use logging config from kuksa-python-sdk #22
Use logging config from kuksa-python-sdk #22
Conversation
32f2ed2
to
4e2836b
Compare
@@ -65,7 +65,7 @@ def start(self): | |||
|
|||
self._kuksa = KuksaClientThread(self._client_config) | |||
self._kuksa.start() | |||
self._kuksa.authorize() | |||
self._kuksa.authorize(token_or_tokenfile=self._token_path) |
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.
Previously we did not consider what token was given in the config file, it worked anyway as kuksa-python-sdk had a default one which was the same one as we used in tests. This is an example on what we need to do to update client to latest kuksa-client. It should only affect VISS/websocket, but I assume we want to make sure thatw e support Websocket at least until end of year when Kuksa Server reaches end of life
Will require an updated kuksa-client to work
It does not come from this PR, it is from this code: https://github.com/eclipse-kuksa/kuksa-can-provider/blob/main/dbcfeeder.py#L306 |
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.
Did some manual testing, looking fine.
lgtm 🍰
Uses logging config from
kuksa-python-sdk
.