Our new how-to guide will get you up and running with PE and Splunk using the Splunk HEC module. Once installed, you'll be able to view and analyze data from Puppet in Splunk with the Puppet Report Viewer.
Give it a try and let us know what you think in the #forge-modules channel in our community Slack!
Today, we're excited to introduce a redesigned Forge home page!
The new home page showcases the most significant change to the Forge's design since since our last refresh in 2018.
We hope you'll enjoy exploring Featured modules (hand-picked by the Forge team!), seeing today's most Recently updated modules, and perusing our growing collection of how-to articles.
What's next? Over the next few months, we'll be rolling out the new look to the rest of the Forge, along with some new features we think you will love.
Do you have a suggestion or comment? Please help us improve the Forge experience by giving your feedback in our community slack, on Twitter via @puppetforge, or emailing us at forge@puppet.com.
We recently resolved an issue that was causing the "Compatibility" and "Scores" tab content for modules to not render correctly.
The root cause was a recent update to one of the Javascript libraries that we use and our not realizing the update wasn't fully backwards-compatible with the previous version. We have now updated all the relevant code to be compatible with the new version. Please let us know in our community slack or via email at forge@puppet.com if you continue to see any problems.
We have a new, IPv6-enabled hostname for the Forge API now in beta and ready for you to try. It’s available at https://forgeapi-cdn.puppet.com and you can configure a few common tools to use this hostname as follows:
For Puppet Enterprise users, in r10k or Code Manager, specify forge_settings in Hiera:
pe_r10k::forge_settings:
baseurl: 'https://forgeapi-cdn.puppet.com'
or
puppet_enterprise::master::code_manager::forge_settings:
baseurl: 'https://forgeapi-cdn.puppet.com'
If you are an open source Puppet user using r10k, you'll need to edit your r10k.yaml directly or set a param for the open source r10k module:
forge:
baseurl: 'https://forgeapi-cdn.puppet.com'
or
$forge_settings = {
'baseurl' => 'https://forgeapi-cdn.puppet.com',
}
In Bolt, set a baseurl for the Forge in bolt.yaml:
puppetfile:
forge:
baseurl: 'https://forgeapi-cdn.puppet.com'
If you are interested, please give it a try and if you run into any problems let us know in our community slack or email us at forge@puppet.com.
Learn how you can easily configure and deploy Oracle Database 19c using Puppet with tools from Enterprise Modules in our new how-to guide!
If you're managing other Oracle services or software, we encourage you to check out more of the tools available from Enterprise Modules on the Forge, and visit their site for more details.
In an effort to ensure secure access to the Forge and adhere to SSL certificate best practices, we've recently dropped usage of our legacy *.puppetlabs.com wildcard certificate. For most users, this won't change anything about how you interact with the Forge.
Users who are utilizing an older client without support for server name indication (SNI) to access modules on the Forge may need to configure their client to point to the Forge at forgeapi.puppet.com, rather than forgeapi.puppetlabs.com (e.g. puppet module install --module_repository=https://forgeapi.puppet.com puppetlabs/apache). This may include Puppet Module Tool in version 3.8 and below of Puppet.
If you’re running into new issues accessing the Forge and you use an older client without SNI, let us know in the #forge-modules channel in our community Slack or email us at forge@puppet.com, and we’ll do our best to help you troubleshoot.
We're excited to share our new Windows Collection page! It includes some of our favorite resources on using Puppet with Windows, along with how-to guides and modules specifically for use on Windows.
As always, your questions and feedback are welcome in the #forge-modules channel in our community Slack. We'd love to hear what you think!
The Forge JSON API now includes information about a module's Bolt plans in API responses. Read more in our documentation on listing the plans in a module version or fetching details for a specific plan.
Responses for other endpoints (for fetching a module, for example) have been updated with links to the plan endpoints where appropriate for convenience.
Modules on the Forge site that include Bolt plans now feature a "Plans" tab, which lists all available plans and their parameters. See our LVM module's Plans tab for an example.
If you're a module author and you don't see your plan parameters documented on the Forge, you may need to add the right doc comments to your code -- our puppet-strings documentation can get you started.
We recently made a change to improve responsiveness of the Forge API and website.
Over time, we had noticed that requests from a small number of IP addresses were able to noticeably impact performance for both the Forge API service and website. Previously, we implemented a form of soft rate limiting, where clients with a large number of requests over a given period of time were placed into a separate, slower queue for receiving responses.
After several months of evaluation, we determined that even with our soft rate limiting implementation, some clients were still able to impact other traffic by generating a large number of requests. In January, we added a hard rate limiting implementation such that clients who make a very large number of requests over a short period of time are first added to the soft rate limiting queue, and after maintaining a high number of requests for a period of time, will be hard rate limited and receive HTTP 429 Too Many Requests responses for a 10 minute period.
This change has improved response times for typical Forge usage, but please let us know at forge@puppet.com if you believe your usage is being unduly hard rate limited.