remote/config: simplify ResourceConfig template loading #1455
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.
Description
ResourceConfig passes a template loader with the directory name of the resource (exporter) config to
jinja2.Environment()
. Instead of using the Environment's loader to load the actual config, the config file is opened and read from manually and its content is then passed tojinja2.Environment.from_string()
.Change that by using the designated
jinja2.Environment.get_template()
method to load the config.Checklist