Error when mounting file to data directory

[regisphilibert]

What version of Hugo are you using (hugo version)?

$ hugo v0.83.1-5AFE0A57+extended darwin/amd64 BuildDate=2021-05-02T14:38:05Z VendorInfo=gohugoio

Does this issue reproduce with the latest release?

Yes

The problem

When trying to use file mounts on the data directory...

module:
  mounts:
  - source: data
    target: data
  - source: netlify.toml
    target: data/netlify.toml

Hugo produces the following error:

Error: add site dependencies: create deps: create PathSpec: build filesystems: this fs supports directories only

This would be tremendously helpful, as user could inspect from hugo's site.Data, package.json, netlify.toml, .forestry/config.yaml and many other repo's root config files.

PS: I seem to recall threads mentioning that the problem/limitation was known but I could not find any existing GH issue.

[davidsneighbour]

I saw this error myself this week and it disappeared after I removed the upper data/data mount (lines 3 and 4) and mounted everything explicitly, not only one file. But I am not sure if that introduced any other issues yet.

[davidsneighbour]

I take my comment back, the issue persists with or without extra data-mount and I am able to mount files for instance in the assets-directory without the note "this fs supports directories only".

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open. If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.