PROTOTYPE: Magic files to access search results/modified files #357
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.
NOTE FOR REVIEWERS: This is a prototype and should be treated as such, which means: let's review idea/design/feasibility instead of concrete implementation details (but if you do have concrete feedback on the implementation, feel free to leave it as such).
This is another prototype, next to #334, to solve the same thing: allowing
step.run
commands to access specific files.What this prototype does is to create magic files inside the container. The files contain lists of files, one filename per line. By using standard shell scripting, the
run
commands can then access these files.Example campaign spec:
Screenshot
Details
This branch here builds on top of #334. But instead of using templating, it simply makes the data available in temp files that are then mounted into the container.
Drawbacks