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

Include category playbooks directly. #207

Open
ypid opened this issue Nov 1, 2015 · 1 comment
Open

Include category playbooks directly. #207

ypid opened this issue Nov 1, 2015 · 1 comment

Comments

@ypid
Copy link
Member

ypid commented Nov 1, 2015

Example app.yml only consists of a single include. Why not include app/all.yml directly?

Pro:

  • Shell tab complete does directly show results in the directory instead of stopping at app|.
  • Simpler.
@drybjed
Copy link
Member

drybjed commented Nov 2, 2015

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.

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

No branches or pull requests

2 participants