You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, the following settings might cause errors or confusion because there would be two main-modules environments deployed to the same base directory.
This is a bit confusing. There will never be an environment named main-modules. Because the config has prefix set to true for both control repos. So every branch will be prefix either myorg_ or mysource_ and there's never a conflict. And the example environment main-modules is identical to the git repository name, which also confuses.
However, by changing one prefix to "testing", the two environments become more distinct, since the directory would now have a myorg-main-modules environment and a testing-main-modules environment:
That's wrong. r10k uses the prefix, then _, then the branch name. - isn't an allowed character in branch names. If we assume that each repository contains a branch named main-modules the result would be just mysource_main_branch for the second repo and nothing will be deployed for the first repo because it has invalid_branches set to true. Since the - in main-branch isn't allowed, the branch won't be deployed at all.
Describe the Bug
please have a look at https://www.puppet.com/docs/pe/2023.7/r10k_customize_config.html#r10k_configuring_sources-r10k-sources-prefix.
and this is the example config:
This is a bit confusing. There will never be an environment named
main-modules
. Because the config hasprefix
set totrue
for both control repos. So every branch will be prefix eithermyorg_
ormysource_
and there's never a conflict. And the example environmentmain-modules
is identical to the git repository name, which also confuses.That's wrong. r10k uses the prefix, then
_
, then the branch name.-
isn't an allowed character in branch names. If we assume that each repository contains a branch namedmain-modules
the result would be justmysource_main_branch
for the second repo and nothing will be deployed for the first repo because it hasinvalid_branches
set to true. Since the-
inmain-branch
isn't allowed, the branch won't be deployed at all.Expected Behavior
A correct documentation
Steps to Reproduce
Steps to reproduce the behavior:
Environment
Additional Context
_
The text was updated successfully, but these errors were encountered: