We are used r10k deploying an environment with a use of control_branch. When you set the a specific environment it uses the environment brach if it exists else it fetches the default specified in Puppetfile.
When I use g10k with a config parameter it set the branch name with :control_branch filled in and it has more priority then tree attribute, when it clones the git repo it uses the branch control_branch instead of set environment branch.
To solve this I have added a extra parameter to the GitModule struct for a control_branch.
Hey,
We are used r10k deploying an environment with a use of control_branch. When you set the a specific environment it uses the environment brach if it exists else it fetches the default specified in
Puppetfile
.When I use g10k with a
config
parameter it set the branch name with:control_branch
filled in and it has more priority thentree
attribute, when it clones the git repo it uses the branchcontrol_branch
instead of set environment branch.To solve this I have added a extra parameter to the
GitModule
struct for acontrol_branch
.Greetz, Egbert