Skip to content
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

Open
handrus opened this issue May 16, 2015 · 5 comments
Open

Add option to run one manifest or exclude one manifest to run #7

handrus opened this issue May 16, 2015 · 5 comments

Comments

@handrus
Copy link

handrus commented May 16, 2015

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.

@rolfvandekrol
Copy link
Member

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?

@handrus
Copy link
Author

handrus commented May 17, 2015

You're right, probably harder than I first thought.
IMHO it should run dependencies since this is a major component to making a manifest idempotent.
Also if we add a exclude option should it exclude the manifest even if it is a dependency of others?

@rolfvandekrol
Copy link
Member

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?

@handrus
Copy link
Author

handrus commented May 18, 2015

I have one manifest that enable modules. I would need to run it before
reverting features (run just one manifest) after reverting features I would
like to run all manifest but the one that ran previously.
On May 18, 2015 8:19 AM, "Rolf van de Krol" [email protected]
wrote:

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?


Reply to this email directly or view it on GitHub
#7 (comment)
.

@rolfvandekrol
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants