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
I keep DebOps playbooks in a central location under ~/.local/share/debops/ and work in the project directories, so I don't have access to Tab-completion of DebOps playbook (there's a thought...). Anyway, current setup allows you to run, say:
debops app -l host
Which is very similar to how old-style playbooks could be used. I wanted to keep the old command working during the transition, I'm also still not sure about the specific role categories (app, srv, hw, etc.). But sure, we could check out a few solutions, including app/all.yml in site.yml directly would allow for clean up of main playbook directory somewhat.
I think that putting more focus on playbooks is important, especially with the transition from role dependencies. I'm looking for ideas about how to manage that, any tips from playbook use in your own environments are welcome.
Example app.yml only consists of a single include. Why not include app/all.yml directly?
Pro:
app|
.The text was updated successfully, but these errors were encountered: