-
Notifications
You must be signed in to change notification settings - Fork 50
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
-branch should include the repository prefix #132
Comments
I don't understand how you're talking about the For me the How about I'll add a |
Sorry, you are right, I got a bit confused, I mixed up updating only a single environment with using |
…_whitelist (#139) * add an example config with a git repository in which all branches can be resolved * add resolveSourcePrefix() and fix up resolvePuppetEnvironment(), preparation for #132 * add test files * add default purge_levels * fix unTar error messages * add stringSliceContains helper function * add tests for purge_levels and purge_whitelist in different combinations * add support for purge_levels and purge_whitelist * add tests for different purge_level combinations * add support for puppetfile purge_level * add deployment_purge_whitelist * add support for deploy setting hash
I've not added an extra parameter for this, but simply added the possibility to match the branch and the prefix+branch combination here: 48c3303#diff-df78fe67e2c9bffdb3673a5fd14d2bb7R84 Now with v.0.7.0 you should be able to specify the exact branch/environment with |
Awesome. If I have one repo with a prefix and one without a prefix and both contain the same branch, does g10k guarantee that when run with |
Ah, now I understand. I've just tested it and g10k would sync both sources currently as anything else involving the As written previously I'm thinking about adding an additional parameter called r10k always uses the source name + "_" + the branch name of the repository. An example:
This way you should also be able to control which branch of which source you want to deploy. How does this sound to you? |
The branch parameter should honor the prefix if one is configured for a given source. Otherwise if two sources use the same branch name, it is impossible to specify which one is ment. For example if there are two sources, "devel" and "staging", and both have a branch "branchname", I would like to run g10k with
-branch devel_branchname
to exactly specify which branch is ment.The text was updated successfully, but these errors were encountered: