Filesystem not replacing jinja2 tokens (Possible bug?)

@jlyle wrote:

Didn't want to start off with opening a github issue when I wasn't sure if this is a bug or not, so I figured I would post this here first. I have the following template in my configuration:

filter-transferring:
    crossmatch:
      from:
        - filesystem:
            path: '/{{stage_path}}'
            regexp: '^.*[\.-]transferring$'
            recursive: no
            retrieve:
              - files
      fields:
        - title
      action: reject
      exact: yes

Basically, I'm transferring files via SFTP and want them to be ignored until the SFTP transfer is fully complete. Also, I use this logic in a few different tasks, so I made it general by using the set plugin in those other tasks to make an entry field called stage_path. (As for the reason for the "/" before the {{stage_path}} token, this is related to passing flexget config validation and is disussed in the forum thread here)

However, when I try to run this, it appears that the filesystem plugin does not replace jijna2 tokens. Upon running, I get the following in my log:

2016-11-18 11:47 VERBOSE  filesystem    process-shows   Scanning folder /{{stage_path}}. Recursion is set to False.

Please notice, the log entry has the jinja2 token in it, not the replaced value that I would expect to see.

Am I missing something here or does the filesystem plugin just not replace jinja2 tokens? If it does not, is this by design for some reason, or is it a bug?

Posts: 9

Participants: 2

Read full topic