{"action":"created","issue":{"url":"https://api.github.com/repos/puppetlabs/r10k/issues/607","repository_url":"https://api.github.com/repos/puppetlabs/r10k","labels_url":"https://api.github.com/repos/puppetlabs/r10k/issues/607/labels{/name}","comments_url":"https://api.github.com/repos/puppetlabs/r10k/issues/607/comments","events_url":"https://api.github.com/repos/puppetlabs/r10k/issues/607/events","html_url":"https://github.com/puppetlabs/r10k/issues/607","id":160120263,"number":607,"title":"r10k and applications tiers","user":{"login":"fonk","id":4289178,"avatar_url":"https://avatars.githubusercontent.com/u/4289178?v=3","gravatar_id":"","url":"https://api.github.com/users/fonk","html_url":"https://github.com/fonk","followers_url":"https://api.github.com/users/fonk/followers","following_url":"https://api.github.com/users/fonk/following{/other_user}","gists_url":"https://api.github.com/users/fonk/gists{/gist_id}","starred_url":"https://api.github.com/users/fonk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fonk/subscriptions","organizations_url":"https://api.github.com/users/fonk/orgs","repos_url":"https://api.github.com/users/fonk/repos","events_url":"https://api.github.com/users/fonk/events{/privacy}","received_events_url":"https://api.github.com/users/fonk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-06-14T08:03:44Z","updated_at":"2016-06-16T22:35:25Z","closed_at":null,"body":"Hi!\r\n\r\nMaybe this topic would better fit on the mailing list, but unfortunately users without google account are locked out...\r\n\r\nWe implemented the concept of application tiers and puppet environments mentioned here: http://garylarizza.com/blog/2014/03/26/random-r10k-workflow-ideas/ and it works great for us so far. But we're now hitting the following problem and I'd like to know if there's a solution that's better supported by r10k or if we're doing things wrong.\r\n\r\nWe have one or sometimes two puppet environments: env_prod and maybe env_test, which mainly just include the Puppetfile (and thus the modules) and are used for testing puppet dsl code. We check them out using \"r10k deploy environment env_prod -p\" and everything's fine.\r\nOur application tiers are called dev, test and prod. We've multiple teams committing hiera-code in different repositories, for example team A supplys hiera-config for App1 and App2 via repo \"TeamA\" and team B supplys hiera-config for App3 via repo \"TeamB\". At the moment every team repo has the branches dev, test and prod.\r\n\r\nThe problem is, that we'd like to deploy the hiera-code for the Apps independently. If we now run \"r10k deploy environment dev\", the checked-in code for all three applications gets checked out. We tried to rename the branches like app1_dev, app2_dev, app3_dev, but are not quite happy with that (mainly because changes to apps of the same team are often the same and can't be done in one commit if they're in different branches, which makes reviews more complicated...).\r\nIs there any (planned) way to tell r10k to just checkout a branch of one named repository? Is r10k the wrong tool for checking out hiera-configs? I'm curious what you think about it...\r\n\r\nBest regards,\r\nFrank"},"comment":{"url":"https://api.github.com/repos/puppetlabs/r10k/issues/comments/226633649","html_url":"https://github.com/puppetlabs/r10k/issues/607#issuecomment-226633649","issue_url":"https://api.github.com/repos/puppetlabs/r10k/issues/607","id":226633649,"user":{"login":"fonk","id":4289178,"avatar_url":"https://avatars.githubusercontent.com/u/4289178?v=3","gravatar_id":"","url":"https://api.github.com/users/fonk","html_url":"https://github.com/fonk","followers_url":"https://api.github.com/users/fonk/followers","following_url":"https://api.github.com/users/fonk/following{/other_user}","gists_url":"https://api.github.com/users/fonk/gists{/gist_id}","starred_url":"https://api.github.com/users/fonk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fonk/subscriptions","organizations_url":"https://api.github.com/users/fonk/orgs","repos_url":"https://api.github.com/users/fonk/repos","events_url":"https://api.github.com/users/fonk/events{/privacy}","received_events_url":"https://api.github.com/users/fonk/received_events","type":"User","site_admin":false},"created_at":"2016-06-16T22:35:25Z","updated_at":"2016-06-16T22:35:25Z","body":"Hi! Thanks for you answer, but both mentioned features seem to bind the hiera data more to the control repo, i.e. the puppet environment. IMHO that's the opposite of what gary said in his blog post.\r\n\r\nWe need a way to check out multiple repos that supply hiera data with more control. At the moment it seems that the only way to control which repo get's checked out is to use different branch names in every repo."}}
{"actor":{"display_login":"fonk"}}