RSE-812: Fix: not importing logs from s3logstore #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ontext.outputfilepath if references an s3 object
|
Waiting for core 4.17.2-rc1 to be released to set the correct dependency |
L2JE
force-pushed
the
rse740-not-importing-logs-from-S3logstore
branch
from
5f8aca2 to
72a0286
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ticket: https://pagerduty.atlassian.net/browse/RSE-740
Depends on: rundeck/rundeck#8583
Support the use of
outputfilepathexecution context variable to access log files in case theisRemoteFilePathvariable istrue, meaning is an imported execution.