Is it possible to provide a (partial) configuration via list of parameters as part of the cruft create command or as a parameter that points to a config file? Or is the only option to skip the prompts and use the defaults from the repository?

For example, cruft update command has a --variables-to-update argument which takes a JSON string of parameters to set:

cruft update --checkout dev --variables-to-update '{ "docker_compose_path": "docker compose" }'

I tested the promptless deployment as instructed in the new docs, and it worked as expected. I also pulled the branch and verified the new tests pass.

The failing mypy tests should be resolved after rebasing on dev.

Is it possible to provide a (partial) configuration via list of parameters as part of the cruft create command or as a parameter that points to a config file? Or is the only option to skip the prompts and use the defaults from the repository?

For example, cruft update command has a --variables-to-update argument which takes a JSON string of parameters to set:

cruft update --checkout dev --variables-to-update '{ "docker_compose_path": "docker compose" }'

Yes it is possible to skip the prompts while overriding the defaults. Use cruft create with these options as an example: --no-input --extra-context '{"nginx_server_name": "dioptra2.example.com"}'

Nice! I confirmed that works. Can we add it to the documentation?

Can we also suggest the user may want to put their deployment config in a file and provide it like this:

cruft create https://github.com/usnistgov/dioptra --checkout dev \
  --directory cookiecutter-templates/cookiecutter-dioptra-deployment --no-input --extra-context "`cat deployment-config.json`"