Add optional env vars config option #29
Merged
Conversation
This file contains 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
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.
Almost everything in TeslaMate is configured via env vars and whilst this addon does a good job of exposing most of them as config options, there are some which it doesn't and may not. Having this new option allows advanced users to take advantage of these env vars within this addon.
My motivation is I want to test switching to using the Fleet API (TeslaMate docs) via the Tesla HTTP Proxy addon already running on my HA instance. Once I've got this working, I'll probably add it as an easy config option to this add-on.
This PR also switches to using a specific builder version as the current builder on master is borked.