Hi,
We are attempting to use s3fs as a fileserver backend and I'm having issues finding the files with file.managed.
Typically our states are tested in a standalone minion on a Vagrant machine before being pushed to our production saltmaster (development VMs are also created using standalone minions).
In the minion config file I have added the following:
fileserver_backend:
- s3fs #nothing is cached if s3 is used as is suggested by the documentation
s3.keyid: <keyid>
s3.key: <key>
s3.buckets:
- <target_bucket>
The bucket has the following directory structure:
<target_bucket>/base/<file>
<target_bucket>/dev/<file>
When I run a state the output on the minion indicates that s3 is being cached and I can see the files being downloaded (additionally, the files are in /var/cache/salt/minion/s3cache). However if we try to use file.manage with the s3 file as the source an error is returned saying the file can't be found. The state looks like:
/path/to/file:
file.managed:
- source: salt://<target_bucket>/<file>
I've tried adding the bucket to base or dev environments in the config file with no difference.
Is the target path correct? Any guidance into how to further debug the issue would be appreciated.
Cheers,
Tyler