Can the `Remote Archive` type project support symbolic link files during extraction?

[blackshy]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I might not receive a timely response.

Feature type

New Feature

Feature Summary

The current issue found with using the "Remote Archive" type project is that when the archive contains symbolic links, the symbolic links are removed during extraction and replaced with empty files.

Select the relevant components

• UI
• API
• Docs
• Collection
• CLI
• Other

Steps to reproduce

For example, when using the release archive of kubespray, an error occurs during execution. Upon investigation, it was found that library/kube.py became an empty file, whereas it was expected to be a symbolic link pointing to ../plugins/modules/kube.py.

Current results

For example, when using the release archive of kubespray, an error occurs during execution. Upon investigation, it was found that library/kube.py became an empty file, whereas it was expected to be a symbolic link pointing to ../plugins/modules/kube.py.

Sugested feature result

For example, when using the release archive of kubespray, an error occurs during execution. Upon investigation, it was found that library/kube.py became an empty file, whereas it was expected to be a symbolic link pointing to ../plugins/modules/kube.py.

Additional information

No response

[thedoubl3j]

I think this is a valid use case since the expectation is that these symbolic links are maintained. One question since I am unfamiliar with Kubespray, given that it has the pattern of "library/somepythonfile" is this using the old method of packaging modules into roles?

Either way, the main issue is still apparent and clear.

[thedoubl3j]

one request though @blackshy what version are you currently running and also can you confirm this behavior on devel?