Ignore `@ hashed` directory when performing disk scan.
In gitlab!42461 (merged) we store zipped pages site version on the same top directory as other pages content. But add @hashed
to avoid name collision with namespaces.
IIRC pages currently recusively scans all subdirectories in shared/pages
, so we need exclude shared/pages/@hashed
.
It may sound irrelevant for .com, since we disabled this disk scan completely. But it's not true for self-managed instances, and once we enable feature flag responsible for creating pages deployments this directory will appear on self-managed. This may create performance problem and maybe some security risks(unlikely though).
But maybe pages will just not find config.json
file there and ignore this directory automatically, but that's need to be tested.
Edited by Vladimir Shushlin