I found a puppet module whose authors just added a bunch of modifications that I would otherwise have to make myself, manually.
This literally occurred 20 hours ago.
I have downloaded the master branch to a zip file, extracted it to my modules folder, and run puppet module build --verbose /etc/puppet/modules/arioch-redis
, to no avail.
I understand that this is definitely not normal behavior, but I feel this question deserves some attention.
There is definitely a use case for using a module from source, especially in projects that move quickly, or rely on quick feedback.
I have done some research on this, and please feel free to ask, "have you looked into X" questions in the comments.
For instance, I looked over https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#build-your-module, but it seems mainly geared toward uploading a module to the Forge, rather than installing locally from source.
Plus, my attempt fails at the "Build Your Module" section.
All three of the following seem to answer this question with "install librarian-puppet", but given that we can write our own modules, it seems silly to have to use librarian-puppet
to use the source code from a publicly available git repository to use a simple module:
Changing puppet module source (I'm looking for an answer to what happens after the OP would create the private repo in that answer. )
How to install a puppet file from a local repo with puppet module install (My Excuse: I don't need to use only the puppet module install
tool. I can use other puppet tools, too.)
Using puppet module straight from a cloned repo (My Excuse: Answer does not seem relevant to this question.)
Installing a puppet module from a manifest script (My Excuse: Again, the best answer, which I think is perfect for that question, is "don't use Puppet for this, find a workaround." In this case, the workaround was to have Vagrant partially use Shell Provisioning.)
If this really is a duplicate, or a summary, please say so in the comments, and maybe I can explain. Edits welcome!
Do I need to hack the metadata.json
contents?
Should I clone this repository somewhere and link it into my own temporary Forge account, or something?
Summary:
How might I get the veeeeerry latest build of the module, when it's passing in Travis on its Git repository, but before the Forge makes it available?