🐛 Describe the bug
If scaf fails to run, it forget all options previous chosen and forces the user to reenter them.
💭 Expected Behavior
Iterative fixes
- populate a config file /tmp/scaf-{template-name}-answers.yaml with old choices (in tmp?) Advertise it's existence on failure.
- Add a flag to use config file ala
--project-config=answers.yml
🔁 Steps To Reproduce
- induce a setup error that occurs in setting up a template (ie turn docker off on full-stack-template)
- run again
📝 Additional context
Fundamentally this is a copier layer problem. -C will skip cleanup leaving answers.yml and rendered template, no flag and it cleansup both.
Without changing copier to maintain a bit state between runs, the best solution, though slightly hacky, would be to do clean up on failure in our wrapper script, saving the answers file and prompting the user to use it (either on error or when the next run occurs).
📜 Relevant log output
📸 Screenshots
z
🐛 Describe the bug
If scaf fails to run, it forget all options previous chosen and forces the user to reenter them.
💭 Expected Behavior
Iterative fixes
--project-config=answers.yml🔁 Steps To Reproduce
📝 Additional context
Fundamentally this is a
copierlayer problem.-Cwill skip cleanup leaving answers.yml and rendered template, no flag and it cleansup both.Without changing copier to maintain a bit state between runs, the best solution, though slightly hacky, would be to do clean up on failure in our wrapper script, saving the answers file and prompting the user to use it (either on error or when the next run occurs).
📜 Relevant log output
📸 Screenshots
z