I hope my question is not too stupid, but I´m a Puppet Beginner…
Lets say I have published some Puppet Modules from Forge in a Content View
called "Puppet", so I have them now under
/etc/puppet/environments/KT_ORG_Lifecycvle_Puppet_Version, what is now the
recommeded way to edit the code in case its needed (e.g. init.pp)?
I´m sure to edit the init.pp in all 4 KT_xxx (Lib,Dev,Test,Prod) is the
wrong way because its an overhead and I will loose the updates when the
next publish will be performed, my previous way was to remove it from the
Content View "Puppet" and adding it manually via "puppet module install
xxx" to /etc/puppet/modules and afterwards to re-import it. But this way
would break the Version Control, so my plan is to have etckeeper/git or to
implement r10k over Katello in order to overcome it…
The question now is how you guys are managing it currently and/or if some
approvement from Katello R&D is planned for the future to improve such
behavior?
Thanks,
Christian
It sounds to me like you need to fork the module and have katello pull it
in from your git repo rather than from the forge. Or if the module is
flexible enough, create a wrapper module around it (like the profile/role
pattern) that passes in the things you need to make it work for your
environment.
Matt
···
On Tue, May 5, 2015 at 2:12 AM, wrote:
I hope my question is not too stupid, but I´m a Puppet Beginner…
Lets say I have published some Puppet Modules from Forge in a Content View
called “Puppet”, so I have them now under
/etc/puppet/environments/KT_ORG_Lifecycvle_Puppet_Version, what is now the
recommeded way to edit the code in case its needed (e.g. init.pp)?
I´m sure to edit the init.pp in all 4 KT_xxx (Lib,Dev,Test,Prod) is the
wrong way because its an overhead and I will loose the updates when the
next publish will be performed, my previous way was to remove it from the
Content View “Puppet” and adding it manually via “puppet module install
xxx” to /etc/puppet/modules and afterwards to re-import it. But this way
would break the Version Control, so my plan is to have etckeeper/git or to
implement r10k over Katello in order to overcome it…
The question now is how you guys are managing it currently and/or if some
approvement from Katello R&D is planned for the future to improve such
behavior?
Thanks,
Christian
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
As Matthew noted, you'll want to manage updates to the modules outside of
what Katello/Pulp has "laid down". The recommended approach would be to
fork the modules, make modifications via git and then use the puppet module
builder from Pulp to prepare them properly for importing into Katello. See
[1] for a walk through of how to do this.
Feedback on user workflows in this area are greatly appreciated.
Eric
[1] http://www.katello.org/docs/2.2/user_guide/puppet_integration/index.html
···
On Tue, May 5, 2015 at 8:04 AM, Matthew Hyclak wrote:
It sounds to me like you need to fork the module and have katello pull it
in from your git repo rather than from the forge. Or if the module is
flexible enough, create a wrapper module around it (like the profile/role
pattern) that passes in the things you need to make it work for your
environment.
Matt
On Tue, May 5, 2015 at 2:12 AM, ehartchr@gmail.com wrote:
I hope my question is not too stupid, but I´m a Puppet Beginner…
Lets say I have published some Puppet Modules from Forge in a Content
View called “Puppet”, so I have them now under
/etc/puppet/environments/KT_ORG_Lifecycvle_Puppet_Version, what is now the
recommeded way to edit the code in case its needed (e.g. init.pp)?
I´m sure to edit the init.pp in all 4 KT_xxx (Lib,Dev,Test,Prod) is the
wrong way because its an overhead and I will loose the updates when the
next publish will be performed, my previous way was to remove it from the
Content View “Puppet” and adding it manually via “puppet module install
xxx” to /etc/puppet/modules and afterwards to re-import it. But this way
would break the Version Control, so my plan is to have etckeeper/git or to
implement r10k over Katello in order to overcome it…
The question now is how you guys are managing it currently and/or if some
approvement from Katello R&D is planned for the future to improve such
behavior?
Thanks,
Christian
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
