Use relative path instead of absolute path in symlink_path
for the out file plugin
#4904
+3
−1
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.
Which issue(s) this PR fixes:
There is no particular issue associated. If necessary I can create one.
What this PR does / why we need it:
This PR moves from an absolute link to a relative link for
symlink_path
parameter. Otherwise, this does not work in a dockerized environment where the path is wired to the the outside of the container.I can also add an additional parameter to switch between absolute and relative linking if necessary and/or desired.
Docs Changes:
I think doc changes are not necassary. However, as far as I read it the documentation does not state whether its an absolute or relative link and it might be useful to add in the scope of this PR.
Release Note:
Uses relative link for
symlink_path
in the out file plugin.