Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save the Tale Run Confiuration #438

Open
ThomasThelen opened this issue Jan 15, 2021 · 0 comments
Open

Save the Tale Run Confiuration #438

ThomasThelen opened this issue Jan 15, 2021 · 0 comments

Comments

@ThomasThelen
Copy link
Member

When users perform a Recorded Run (RR) they need to specify the 'driver' script that executes their workflow, which we call the Run Configuration. This is a parameter that should be able to be changed each Recorded Run (Recorded Run 'A' doesn't need to use the same Run Configuration as Recorded Run 'b'). For this reason, the Run Configuration should be saved with each 'Run'. Note that this would require versioning 'Runs' instead of 'Versions'.

Since this parameter is essential for performing the recorded run, it needs to be saved

  1. Within the Whole Tale system so that the Recorded Run can be run again (vs ephemerally passing it to the RR)
  2. Within the manifest of exported Tales so that imported Tales with recorded runs can be re-run, using the same run configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant