Fix token file save path for VIN-specific tokens - #2
Open
cook1e0 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1
This patch ensures that tokens for VIN‑specific vehicles are saved in the directory specified by FORDLOGGER_TOKEN_DIR instead of the working directory.
Previously, auth.py wrote files like tokens_.json to whatever directory the program was run from, while later runs looked for VIN token files in the configured token directory. In Docker deployments this mismatch meant that a successful auth flow could still fail later because the token file wasn’t persisted or found.
The patch introduces an os import and writes the VIN token file into the directory pointed to by FORDLOGGER_TOKEN_DIR, creating it if necessary.
The fallback behaviour that writes to tokens.json remains unchanged. After applying this change, the token file is persisted in the correct location and discovered properly on subsequent runs.