Re: v7.8beta [testing] is released!
Posted: Thu Feb 09, 2023 2:31 pm
I guess you could confirm if your original code worked in 7.8beta2...
Like I say, I also experienced this issue since 7.8beta3.. Before I was using:
Code: Select all
/tool fetch keep-result=no url=("http://url")
Now I'm using this (based on dksoft's suggestion), which works:
Code: Select all
/tool fetch url=("http://url") as-value output=none
I'm definitely concerned about whether anything is being written to nand/disk on either of these approaches... ?
The documentation (https://wiki.mikrotik.com/wiki/Manual:Tools/Fetch) states:
Since default for keep-result is yes, and yes creates a file, then logically, wouldn't it be a bad idea to remove keep-result=no, since if the documentation is accurate, that would imply a file is being created somewhere? 🤔
keep-result (yes | no; Default: yes) If yes, creates an input file.
output (none|file|user; Default: file) Sets where to store the downloaded data.
none - do not store downloaded data
file - store downloaded data in a file
user - store downloaded data in the data variable
But my understanding of setting output=none is that it does the same thing? So is there something going on behind the scenes that we don't know, or are these literally two redundant settings and they were "in the process" of removing keep-result and some changes slipped through the cracks without showing up in the changelog?
What is interesting, is passing keep-result=no, with output=none:
Code: Select all
[admin@MikroTik] > /tool/fetch url=http://url as-value output=none keep-result=no
failure: please use 'output' option
