You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tagging @rmccue because after yesterday, I think I don't get along well at all with Puppet (and especially the Puppet docs). An outside opinion would be helpful.
We can't run an import unless the Importer plugin is installed and active. puppet-wp doesn't seem to let me use unless or onlyif on any of its exposed tasks, so chaining appears to be the only way I can ensure that this occurs. Right now we're doing this (simplified for brevity):
Is this the best way to achieve this? What I want to be able to do is to say,
Guarantee me that the importer plugin is installed and active
THEN, if clean is set, wipe the content
THEN, import the content
I feel this should be achievable but nothing I can determine about this $@%$%! piece of trash configuration management tool explains in human-readable terms how to make it happen.
(Ansible, if you're out there watching, 💕. I miss you. Come home.)
The text was updated successfully, but these errors were encountered:
We discussed this a bit in Slack, but to go into a bit further detail here:
Puppet is entirely declarative, so there's no concept of if x, do y (apart from compile-time things), generally speaking. Instead, you say how you want the universe to look, and Puppet works out the internals.
For something like this, what you'd want to generally do is have a resource like:
definewxr::content(
$path= $title,
) {
# ...
}
Internally, this would then work out how to make the universe match the declared state. You can break out into Ruby if you want to.
Without doing that, you'd want something like this:
Tagging @rmccue because after yesterday, I think I don't get along well at all with Puppet (and especially the Puppet docs). An outside opinion would be helpful.
We can't run an import unless the Importer plugin is installed and active.
puppet-wp
doesn't seem to let me useunless
oronlyif
on any of its exposed tasks, so chaining appears to be the only way I can ensure that this occurs. Right now we're doing this (simplified for brevity):Is this the best way to achieve this? What I want to be able to do is to say,
I feel this should be achievable but nothing I can determine about this $@%$%! piece of trash configuration management tool explains in human-readable terms how to make it happen.
(Ansible, if you're out there watching, 💕. I miss you. Come home.)
The text was updated successfully, but these errors were encountered: