Follow symlinks when copying automation repositories #49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Allows resource-dispatcher to clone and copy repositories containing symlinks with
shutil.copytree
How should this be tested?
The infra-ansible repository is an example of one that will fail at this step due to symlinks that will recurse to an infinite path.
This seems to run immediately when the first task is received by the dispatcher and will cause the /tmp dir to recursively fill up with symlinks, for example:
Is there a relevant Issue open for this?
N/A
Other Relevant info, PRs, etc.
Please provide link to other PRs that may be related (blocking, resolves, etc. etc.)
People to notify
cc: @redhat-cop/tool-integrations