Prevent recursive variable expansion for paperless_ngx_conf_filename_format
#242
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
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.
It seems that even when wrapped between
{% raw %}...{% endraw %}theansible.builtin.lineinfiletask interprets the paperless-ngx specific placeholde syntax as Jinja variable expressions and tries to expand them. This causes trouble when using the paperless-ngx specific text template syntax inpaperless_ngx_conf_filename_formatas ansible and paperless have identical syntaxes in this regard.This recursive variable expansion can be prevented by escaping the loop item which renders the line for the filename format. (For a more details, see #241.) Again I'm not sure if this is the intended way. But if so, I am happy to assist.