Re: debops install methods, updates and rolling release
On cze 04, Jan Kowalsky wrote:
> Yes, at the moment the role always checks out the
'master' branch because
> that's what the 'debops-update' script does. Looks like there's no
support for
> changing the branch at the moment in the role. But that's a good idea to
> implement.
but meanwhile nothing speaks against just checking out a tag?
Sure, after the repository is cloned you can switch to a specific tag. Running
'debops-update' will just result in 'git pull' in that case, so with a
tag
nothing should change. And if you switch to abranch, for example 'stable-2.0',
you have an easy way to get the latest updates.
> Just a tongue-in-cheek... you are setting up DebOps using DebOps
after all.
> :-)
ok. yes. But what's the difference to [debops_service_debops]? And
actually: I can't find any reference to [debops_recursively] in the code.
No difference, these are just two Ansible groups for the same playbook.
Cheers,
Maciej