...
They are "executed" in this order. This is very important. Normally the order is exactly what you want, but sometimes it is not. For example you may want a promise in the "commands" section to execute before a promise in "files" section. When this is true, the most straightforward way to to break your bundle into two separate bundles and then change the order in the "inputs" order. Unfortunately your variables are now spread across the two bundles.
Here's an example
Before breakup
| Code Block |
|---|
bundle agent foo {
files:
"/some/file"
classes => if_repaired("do_this");
# BROKEN!! because files is executed *after* classes
classes:
do_this::
"bar" expression => fileexists("/some/other/file");
}
|
After breakup
| Code Block |
|---|
bundle agent foo {
files:
"/some/file"
classes => if_repaired("do_this");
methods:
do_this::
"any" usebundle => "bar";
}
bundle agent bar {
classes:
# this works only because "if_repaired" defines "do_this" in global context
# otherwise you'd have to use "$(foo.do_this)"
do_this::
"bar" expression => fileexists("/some/other/file");
}
|
Create an empty directory
No obvious, but here's how
| Code Block |
|---|
bundle agent generate_certs {
files:
any::
"$(sipx.SIPX_VARDIR)/temp/cert-temp/."
create => "true";
}
|
Control order of promises.
All the plugins are executed in alphabetical order in /use/share/sipxecs/cfinputs/plugin.d but sometimes you want to ensure a promise is executed before your promise and you'd rather not have to change the name of your modules. All you need to do is use any bundles that you require to be run before your module. Those modules will only be run once, just before your module.
Example:
| Code Block | ||
|---|---|---|
| ||
bundle agent aaaa {
methods:
"any" usebundle => zzzz;
reports:
any::
"This will get executed after zzzz but only once";
}
|
| Code Block | ||
|---|---|---|
| ||
bundle agent zzzz {
reports:
any::
"This will get executed before aaaa_otherstuff_after_zzzz but only once";
}
|