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
assume you have multiple puppet modules that you share with others and one "project" module that implements project-level specific logic.
you do not have a real control repository but rather your project module is your control repo as well.
you have the following branches in your project module: master, feature1
now one of the shared modules has another branch, say feature2 and you want to test feature2 without touching your own module. how would you do that? it is currently not possible
to ease the development and testing workflow in such cases i want to introduce a new feature, lets call it virtual environments
whenever g10k detects branches in modules that are not in your control repo, it should create an environment symlink to, say, master, or any configurable branch.
this could also be similar to how fallback works, it just puts files from a fallback branch (and does not use symlinks or whatever), but makes sure the environment exists.
i would like to have your opinion on that. for now this is just a rough idea
The text was updated successfully, but these errors were encountered:
I'm just confused as to how your project module that is also your control repo looks. Does it contain the Puppetfile?
I think it would be really helpful if you could create a Git repository here on GitHub of your idea / project repo, so that I could develop against that.
thanks for reaching out to me!
in the meantime i have already developed an implementation for it that i would try to wrap up & test this week and then pull request to you
it is already running fine on some servers for some time
i think it will be much clearer then and we can see if you are fine with it :)
assume you have multiple puppet modules that you share with others and one "project" module that implements project-level specific logic.
you do not have a real control repository but rather your project module is your control repo as well.
you have the following branches in your project module:
master
,feature1
now one of the shared modules has another branch, say
feature2
and you want to testfeature2
without touching your own module. how would you do that? it is currently not possibleto ease the development and testing workflow in such cases i want to introduce a new feature, lets call it virtual environments
whenever g10k detects branches in modules that are not in your control repo, it should create an environment symlink to, say, master, or any configurable branch.
this could also be similar to how
fallback
works, it just puts files from a fallback branch (and does not use symlinks or whatever), but makes sure the environment exists.i would like to have your opinion on that. for now this is just a rough idea
The text was updated successfully, but these errors were encountered: