Closed russmiles closed 3 years ago
I'm going to prioritise this one as it helps automation.
But, for now, I will stick to implementing the command that sets keys in the settings file. I'm not sure yet about installing dependencies (a good idea but also a can of worms if not done well...)
This Issue has not been active in 365 days. To re-activate this Issue, remove the Stale
label or comment on it. If not re-activated, this Issue will be closed in 7 days.
This Issue was closed because it was not reactivated after 7 days of being marked Stale
.
A
configure
command allows the toolkit installation to manage its extensions (plugins and drivers) according to specific versions, and also to manipulate settings (stored in~/.chaostoolkit/settings.yaml
).The idea for the workflow is:
chaos configure -settings key:value key:value -plugins pluginName:1.0.0 pluginName:0.3.0 -drivers driverName driverName:0.4.0
At the moment,
configure
cannot specify a version of the chaos toolkit itself. However it could do this in the future, particularly in the case where a new virtual environment is being specified.Also, the choices in the above workflow could be defaulted with:
-virtualenv
to automatically create a local virtual environment-override
to automatically override any version collisions, preferring the versions specified in the configure command.--no-override
to prefer existing versions over those specified in theconfigure
command, so ignoring any versions that are a collision with what is already present.