Added: --replay-file cli option, for replay file distributing#906
Added: --replay-file cli option, for replay file distributing#906insspb merged 12 commits intocookiecutter:masterfrom
Conversation
|
If people are happy with this idea I will add tests and docs etc. |
|
+1 |
|
Hi @Cadair! 👋 Thank you for your contribution. I'm not sure if this approach is better than using Happy to merge this with tests and docs, if others are OK with this approach. |
|
What's the situation about this idea? Currently, I'm looking for a way to apply a template over and over again through multiple projects, so this new option to specify a replay file will be awesome to me. There is anything that I can do to help merging this? |
|
I have not had a chance to get back to the project that this was a part of. I will try and get to it soon. If you want to speed it up, writing tests and docs for the change in this PR is what needs doing. I will happily merge PRs against my fork with any contributions. |
|
I"m also interested in getting this new option, I think it could help maintainers of templates with several options to reproduce issues. I will try to add the missing parts... |
# Conflicts: # cookiecutter/main.py
Add documentation and tests to replay_file branch
Fix flake8 error
|
I'm very +1 for this feature, seems like a big hole in cookiecutter functionality. Any possibility of merging any time soon? What's missing?
The proposed option is very non-intuitive. This issue is by far the least-surprise approach. Cookiecutter already accepts JSON files for the defaults. Like others have said this would simplify testing immensely. I might suggest also adding an option to generate a |
|
@Cadair @browniebroke @diegoholiveira @epcim |
|
Awesome thank you for this! |
|
@salotz You are welcome. |
This adds an option to
main.cookiecutterand the CLI to specify a json file to read the replay data from.The motivation for this is to provide a way to run the same replay over different machines, i.e. store the replay in a git repo.