Issue Summary

In Bitbucket 8.x version, the support zips created by the ATST plugin don't capture the "mesh-sidecar/sidecar/log" when the $BITBUCKET_HOME/mesh/log is configured as a valid symlink.

This is reproducible on Data Center: yes

Steps to Reproduce

Able to replicate the issue with Bitbucket 8.0 and 9.4 by setting a valid symlink in the $BITBUCKET_HOME/mesh/log
To recreate:
1. set $BITBUCKET_HOME/log to a valid symlink to a different location

root@53e839aae9dc:/var/atlassian/application-data/bitbucket/mesh# ls -l
total 60
drwxr-xr-x 3 root      root         96 Mar  6 12:05 bin
drwxr-xr-x 4 root      root        128 Mar  6 12:05 config
lrwxr-xr-x 1 root      root         50 Mar  6 12:24 log -> /var/atlassian/application-data/shared/sidecar-log
-rw-r--r-- 1 bitbucket bitbucket 40960 Mar  6 12:29 mesh.mv.db
-rw------- 1 root      root        142 Mar  6 12:25 mesh.properties
-rw------- 1 root      root        142 Mar  6 12:25 mesh.properties.bak
-rw-r--r-- 1 root      root       9934 Mar  6 12:25 mesh.trace.db
drwxr-xr-x 3 root      root         96 Mar  6 12:25 tmp

2. start Bitbucket
3. observe that bitbucket starts and logs are created and updated
4. create a support zip
5. observe the lack of mesh-sidecar/sidecar/log folder

Expected Results

Bitbucket 8.x support zips should capture the "mesh-sidecar/sidecar/log"

Actual Results

Bitbucket 8.x support zip does not capture the "mesh-sidecar/sidecar/log" and it does not follow symlinks for log folders.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available
Similar bug was fixed for application-log -> https://jira.atlassian.com/browse/BSERV-14080