本文介绍了更改木偶模块源的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我查看了 Puppet 的文档,但没有找到任何关于它的建议.我有 Monit 的 Puppet 模块 - https://forge.puppetlabs.com/dhoppe/monit .它已经为 files 文件夹中的某些服务提供了一些预定义的配置 - https://github.com/dhoppe/puppet-monit/tree/master/files/common/etc/monit/conf.d.我想添加更多,但不确定如何以正确的人偶方式进行.

I checked Puppet's documentation but didn't find any suggestions about it. I have Puppet module for Monit - https://forge.puppetlabs.com/dhoppe/monit . It already has some predefined configurations for some services in files folder - https://github.com/dhoppe/puppet-monit/tree/master/files/common/etc/monit/conf.d . I want to add more, but not sure how to do it in the correct puppet way.

是否可以将新的服务配置添加到本地`puppet/module/monit/files/文件夹中?当模块更新到来时,这个文件夹会被覆盖吗?或者也许有更好的方法?

Is it ok to add new service configuration to local `puppet/module/monit/files/ folder? Will this folder be overwritten when update for module comes? Or maybe there is a better way for it?

附注.我的服务不是公开的,因此我无法向原始 dhoppe-monit 存储库发出拉取请求.

PS. My services aren't public wide, so i can't make pull request to original dhoppe-monit repository.

推荐答案

拉取请求是一个很好的关键字.

Pull request is a good keyword.

如果你不能将你的需求发送到上游,你可能希望维护一个私有的分支/分支.是的,您将需要自行适应上游更改,以确保您的添加继续有效.

If you cannot send your requirements upstream, you may wish to maintain a private fork/branch instead. And yes, you will be required to accomodate for upstream changes yourself to make sure that your additions keep working.

除了从头开始编写自己的模块之外,我真的看不出有其他方法可以实现这一目标.

Apart from writing your own module from scratch, I don't really see another way to make this happen.

这篇关于更改木偶模块源的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-10 08:21