[Feature Request] Cruft Compatibility

[GatlenCulp]

Cruft is a simple CookieCutter template management system. Including support for it in CCDS would (correct me if I'm wrong) allow users to pull changes from the CCDS template into their pre-existing CCDS-instantiated project. This happens by saving the initial CookieCutter arguments in a json file when the project is instantiated (say with ccds --cruft) and when running cruft update (say ccds --cruft-update) the new template is ran through CookieCutter with the cached arguments, and merging the new instantiation with the actual project with Git.

For example: CCDS V2.1 is released and contains some updated default tooling some user would like to use on their project that they already used CCDS V2.0 to create. By running something like ccds --cruft-update, the user can pull these changes without having to either add these changes by hand or re-instantiate another CCDS project.

As someone who is making their own CCDS fork, I would really like to see this added since I plan on iterating on my template often and one of the major reasons against using CCDS as a starting point was because of this lack of cruft-compatibility.

(Update: I realize this might be better as a discussion rather than issue)

[pjbull]

I think it probably makes more sense for cruft to support ccds than the other way around (since ccds is basically cookiecutter with some adjustments for features we needed). Because we need these changes, we can't in the near term make CCDS strictly cookiecutter compatible, and it looks like running cruft probably depends on that.

Have you raised an issue there?

[GatlenCulp]

I haven't. I might make one soon, if so I will link it here

[GatlenCulp]

@pjbull I went ahead and wrote an issue on Cruft: cruft/cruft#332