-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to run one manifest or exclude one manifest to run #7
Comments
This is probably a little less easy than it sounds at a first glance. If you specify a manifest, should it run it dependencies first or not? |
You're right, probably harder than I first thought. |
Good questions. Running one manifest with it's dependencies makes sense to me during development, but what would be the use case of excluding manifests? |
I have one manifest that enable modules. I would need to run it before
|
I assume you are not using the rest of Kraftwagen, because Kraftwagen offers a way to manage the enabled modules using the dependencies of the install profile. Given that, why do you need to exclude the module-enabling manifest? Because manifests should be idempotent, that should be no problem to running that manifest again. |
Should be fairly easy to add a options to kw-m to run only the desired manifest.
Optionaly exclude one manifest to run should also be desirable.
The text was updated successfully, but these errors were encountered: