Publishing modules on the Puppet Forge
This version of Puppet is not included in Puppet Enterprise. The latest version of PE includes Puppet 4.9.
The Puppet Forge is a community repository of modules, written and contributed by Puppet Open Source and Puppet Enterprise users. Using the Puppet Forge (Forge) is a great way to build on the work others have done and get updates and expansions on your own module work. This document describes how to publish your own modules to the Forge so that other users can install them, as well as how to maintain your releases once published.
- Continue reading to learn how to publish your modules to the Puppet Forge.
- See “Module Fundamentals” for how to write and use your own Puppet modules.
- See “Installing Modules” for how to install pre-built modules from the Puppet Forge.
- See “Using Plugins” for how to arrange plugins (like custom facts and custom resource types) in modules and sync them to agent nodes.
- See “Documenting Modules” for a README template and information on providing directions for your module.
This guide assumes that you have already written a useful Puppet module. To publish your module, you will need to:
- Create a Puppet Forge account, if you don’t already have one.
- Prepare your module.
- Write a metadata.json file with the required metadata.
- Build an uploadable tarball of your module.
- Upload your module using the Puppet Forge’s web interface.
A note on module names
Because many users have published their own versions of modules with common names (“mysql,” “bacula,” etc.), the Puppet Forge (Forge) requires module names to have a username prefix. That is, if a user named “puppetlabs” maintained a “mysql” module, it would be known to the Forge as “puppetlabs-mysql”. Be sure to use this long name in your module’s metadata.json file.
However, your module’s directory on disk must use the short name, without the username prefix. (Module directory names cannot contain dashes or periods; only letters, numbers, and underscores). Using the the build action will do the right thing as long as the metadata.json is correct.
Another note on module names
Although the Puppet Forge expects to receive modules named
username-module, its web interface presents them as
username/module. There isn’t a good reason for this, and we are working on reconciling the two; in the meantime, be sure to always use the
username-module style in your metadata files and when issuing commands.
Create a Puppet Forge account
Before you begin, you should create a user account on the Puppet Forge (Forge). You will need to know your username when publishing any of your modules.
- Start by navigating to the Forge website and clicking the “Sign Up” link in the sidebar:
- Fill in your details. After you finish, you will be asked to verify your email address via a verification email. Once you have done so, you can publish modules to the Forge.
Prepare the module
If you already have a Puppet module with the correct directory layout, you can continue to the next step.
Alternately, you can use the
puppet module generate action to generate a template layout. Generating a module will provide you with a sample README and a copy of the
spec_helper tool for writing rspec-puppet tests. It will also launch a series of questions that will create your metadata.json file.
Follow the directions to generate a new module.
Note: In order to successfully publish your module to the Puppet Forge and ensure everything can be rendered correctly, your README, license file, changelog, and metadata.json must be UTF-8 encoded.
Set files to be ignored
It’s not unusual to have some files in your module that you want to exclude from your build. You can exclude files by including them in .gitgnore or .pmtignore. Your .pmtignore or .gitignore file must be in the module’s root directory, and will be read during the build process.
If you have both a .pmtignore and a .gitignore file, the Puppet module tool will read the .pmtignore file over the .gitignore.
Before you build your module, you must make sure that symlinks are either removed or set to be ignored. If you try to build a module with symlinks, you will recieve the following error:
Warning: Symlinks in modules are unsupported. Please investigate symlink manifests/foo.pp->manifests/init.pp. Error: Found symlinks. Symlinks in modules are not allowed, please remove them. Error: Try 'puppet help module build' for usage
Write a metadata.json file
If you generated your module using the
puppet module generate command, you’ll already have a metadata.json file. Check it and make any necessary edits.
If you assembled your module manually, you must make sure that you have a metadata.json file in your module’s main directory.
Build your module
In order for your module to be successfully uploaded to and displayed on the Forge, your metadata.json file must include the following keys:
To build your module:
# puppet module build <MODULE DIRECTORY>. A .tar.gz package will be generated and saved in the module’s pkg/ subdirectory. For example:
# puppet module build /etc/puppetlabs/puppet/modules/mymodule Building /etc/puppetlabs/puppet/modules/mymodule for release /etc/puppetlabs/puppet/modules/mymodule/pkg/examplecorp-mymodule-0.0.1.tar.gz
Throughout the Puppet 3.x series, deprecation warnings were issued for Modulefile. If you still have a Modulefile, it will be treated like any other text file in the root directory of the module. You will need to move any metadata contained in it to the metadata.json.
Upload to the Puppet Forge
Now that you have a compiled
tar.gz package, you can upload it to the Forge. There is currently no command line tool for publishing; you must use the Forge’s web interface. Note: Your tarball must be 10MB or less.
Whether you are uploading a brand new module or a new release of an existing module, follow the steps below to publish your release:
In your web browser, navigate to the Puppet Forge and log in.
Click on “Publish” in the upper right hand corner of the screen.
This will bring you to the upload page:
Click “Choose File” and use the file browser to locate and select the release tarball you created with the
puppet module buildaction. Then click the “Upload Release” link.
A successful upload will result in you being taken to the new release page of your module. Any errors will come up on the same screen. Once your module has been published to the Puppet Forge, the Forge will pull your README, Changelog, and License files from your tarball to display on your module’s page. To confirm that it was published correctly, you can install it on a new system using the
puppet module installaction.
- You must make sure that your metadata is correct and entirely located in metadata.json, otherwise your module will either not display correctly on the Forge or will error out during upload.
- When you release a new version of an already published module, you must increment the
versionfield in the metadata.json file (ensuring you use a valid semantic version).
- You are highly encouraged to fix any problems or mistakes with your module by issuing another release.
Delete a release
At some point, you might want to delete a release of your module. You can accomplish this easily from the Forge’s web interface.
A deleted release will still be downloadable via the Forge page or Puppet module tool (PMT) if a user requests the module by specific version. You cannot delete a released version and upload a new version of the same release.
Follow the steps below to delete your release:
In your web browser, navigate to the Puppet Forge and log in.
Click Your Modules.
Go to the module page of the module whose release you want to delete.
Locate Select another release, choose the release you want from the drop down, and click Delete.
You will be taken to a new page. On that page, you must supply a reason for the deletion. Note: Your reason will be visible to users on the Forge.
Click Yes, delete it.
On your module page, you will see a banner confirmation of the deletion.
Once you receive the confirmation banner, your release is officially deleted!
Downloading a deleted release
It is still possible to download a specific release of a module, even if it has been deleted. If you check the Select another release drop down, the release is still an option in the menu, but is marked as deleted.
If you select the deleted release, a warning banner will appear on the page with the reason for deletion. However, you can still download the deleted release using the PMT or by clicking Download.
Searching for a deleted module
If the only release of a module is deleted, or if all the releases of a module are deleted, the module will still show up in the Forge’s search under some circumstances.
For example, puppetlabs-appdirector has only one release. It is the only result when we search for the word ‘appdirector’.
If that one release is deleted and we search for the word ‘appdirector’, no results are found.
However, if we check the box to Include deleted modules in our search, the appdirector module is found.