Skip to content
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

Fallback-Option for linked=>true #31

Closed
slm0n87 opened this issue Dec 2, 2016 · 1 comment
Closed

Fallback-Option for linked=>true #31

slm0n87 opened this issue Dec 2, 2016 · 1 comment

Comments

@slm0n87
Copy link

slm0n87 commented Dec 2, 2016

The 'link => true' feature from bkuebler in #6 for syncing 'linked' environments is very cool and useful if you are working in predefined environments (dev->prelive->live).
But with this feature you are currently forced to create 'own' branches for every linked module to have a working puppet-environment (working g10k-sync).

So it is not easy to create own branches anymore for testing.

For that a kind of 'link-fallback' would be great.
So that g10k still tries to sync a branch with the same name as the environments branch, but if this does not exist using the fallback-branch.
That fallback-branch could for example be set 'hard-coded' to the default-branch of the git - or could be configured by an additional 'link-fallback'-attribute in Puppetfile.

Thx and Greets
Simon

@xorpaul xorpaul closed this as completed Dec 2, 2016
@xorpaul
Copy link
Owner

xorpaul commented Dec 2, 2016

Feature is already there:

mod 'stdlib',
    :git => 'https://github.com/puppetlabs/puppetlabs-stdlib.git',
    :link => true,
    :fallback => '4.889.x|foobar|master'

Checkout the last additional feature https://github.com/xorpaul/g10k/blob/master/README.md#additional-puppetfile-features

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants