Ordering of commands in main `manifest` is ignored #167

New issue

Closed

opened 2021-11-20 15:20:37 +00:00 by ungleich-gitea · 2 comments

ungleich-gitea commented

2021-11-20 15:20:37 +00:00

Owner

Created by: zilti

It seems 4.1.0 doesn't respect the order of the commands in the main manifest file. Is there a way to force the correct order? Is this a bug or intended behaviour?

*Created by: zilti* It seems 4.1.0 doesn't respect the order of the commands in the main manifest file. Is there a way to force the correct order? Is this a bug or intended behaviour?

ungleich-gitea closed this issue

2021-11-20 15:20:37 +00:00

ungleich-gitea commented

2021-11-20 15:45:23 +00:00

Author

Owner

Created by: zilti

Ah, yes, this variable helped. Thanks!

*Created by: zilti* Ah, yes, this variable helped. Thanks!

ungleich-gitea commented

2021-11-20 15:45:24 +00:00

Author

Owner

Created by: darko-poljak

Daniel,

The order of execution in the manifests does not matter: cdist employs an
idempotent configuration.

If you want to describe that something requires something else, just setup
the variable “require” to contain the requirements.

You can tell cdist to execute all types in the order in which they are
created in the manifest by setting up the variable CDIST_ORDER_DEPENDENCY.
When cdist sees that this variable is setup, the current created object
automatically depends on the previously created object.

See
http://www.nico.schottelius.org/software/cdist/man/latest/man7/cdist-manifest.html

Or do you have issues despite this info above?

All work and no play makes Jack a dull boy
On Jul 3, 2016 12:10 AM, "Daniel Ziltener" notifications@github.com wrote:

It seems 4.1.0 doesn't respect the order of the commands in the main
manifest file. Is there a way to force the correct order? Is this a bug or
intended behaviour?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ungleich/cdist/issues/455, or mute the thread
https://github.com/notifications/unsubscribe/AFDiMf03YfJlq-CYcazeoM92Vq6Spzx8ks5qRuHogaJpZM4JDwoT
.

*Created by: darko-poljak* Daniel, The order of execution in the manifests does not matter: cdist employs an idempotent configuration. If you want to describe that something requires something else, just setup the variable “require” to contain the requirements. You can tell cdist to execute all types in the order in which they are created in the manifest by setting up the variable CDIST_ORDER_DEPENDENCY. When cdist sees that this variable is setup, the current created object automatically depends on the previously created object. See http://www.nico.schottelius.org/software/cdist/man/latest/man7/cdist-manifest.html Or do you have issues despite this info above? **All work and no play makes Jack a dull boy** On Jul 3, 2016 12:10 AM, "Daniel Ziltener" notifications@github.com wrote: > It seems 4.1.0 doesn't respect the order of the commands in the main > manifest file. Is there a way to force the correct order? Is this a bug or > intended behaviour? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > https://github.com/ungleich/cdist/issues/455, or mute the thread > https://github.com/notifications/unsubscribe/AFDiMf03YfJlq-CYcazeoM92Vq6Spzx8ks5qRuHogaJpZM4JDwoT > .