Manage Mozilla products (currently supported: firefox)




1,435 latest version

5.0 quality score

Version information

  • 5.2.0 (latest)
  • 5.1.1
  • 5.1.0
  • 5.0.1
  • 5.0.0
  • 4.1.2
  • 4.1.1
released Mar 12th 2020
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x
  • Puppet >= 5.0.0 < 7.0.0
  • CentOS

Start using this module


simp/mozilla — version 5.2.0 Mar 12th 2020

License CII Best Practices Puppet Forge Puppet Forge Downloads Build Status

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with mozilla
  4. Development - Guide for contributing to the module


This module provides classes to install Mozilla Firefox and Mozilla Thunderbird.

This is a SIMP module

This module is a component of the System Integrity Management Platform, a compliance-management framework built on Puppet.

If you find any issues, they can be submitted to our JIRA.

Please read our Contribution Guide.

This module is optimally designed for use within a larger SIMP ecosystem, but it can be used independently:

  • When included within the SIMP ecosystem, security compliance settings will be managed from the Puppet server.
  • If used independently, all SIMP-managed security subsystems are disabled by default and must be explicitly opted into by administrators. Please review the client_nets and $enable_* parameters in manifests/init.pp for details.

Module Description

This module will only install Mozilla Firefox and Mozilla Thunderbird, depending on the class included.

See for API details.


What mozilla affects

The firefox and thunderbird packages.

Beginning with mozilla

To install firefox:

include 'mozilla::firefox'

To install thunderbird:

include 'mozilla::thunderbird'

init.pp contains no code and including it will do nothing.


Please read our Contribution Guide.

Acceptance tests

To run the system tests, you need Vagrant installed. Then, run:

bundle exec rake acceptance

Some environment variables may be useful:

  • BEAKER_debug: show the commands being run on the STU and their output.
  • BEAKER_destroy=no: prevent the machine destruction after the tests finish so you can inspect the state.
  • BEAKER_provision=no: prevent the machine from being recreated. This can save a lot of time while you're writing the tests.
  • BEAKER_use_fixtures_dir_for_modules=yes: cause all module dependencies to be loaded from the spec/fixtures/modules directory, based on the contents of .fixtures.yml. The contents of this directory are usually populated by bundle exec rake spec_prep. This can be used to run acceptance tests to run on isolated networks.