initial env var ingestion for rev proxy configs #586
+588
−0
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.
I have tested this pretty thoroughly at this point, it is bolt on logic so will not have an effect on any existing setups unless you can think of any possible reason someone would be passing an env var starting with "PROXY_CONFIG_" to a swag container.
The most basic string is incredibly useful to do subdomain setup to a port using a service name as :
This basically just works in most cases subdomain to a port, but all the options are there to get way more complex like in the case of Plex:
The docced examples show the - array member syntax with escaped $ being double $$ and the whole thing being wrapped in single quotes but the object syntax like the plex example above is much more forgiving.
I think this is a good first step and maybe down the line we can look at using jinja templates for the ini generation and get everything in an env var format if possible.