Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

mount_core

Manages mounted filesystems and mount tables.
Project URLRSS FeedReport issues

866,806 downloads

24,095 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.3.0 (latest)
  • 1.2.0
  • 1.1.0
  • 1.0.4
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
released Mar 6th 2024
Passed malware scan
This version is compatible with:
  • Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x
  • Puppet >= 6.0.0 < 9.0.0
  • CentOS, OracleLinux, RedHat, Scientific, Debian, Ubuntu, Fedora, macOS, SLES, Solaris, Rocky, AlmaLinux, Amazon

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'puppetlabs-mount_core', '1.3.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add puppetlabs-mount_core
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install puppetlabs-mount_core --version 1.3.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

puppetlabs/mount_core — version 1.3.0 Mar 6th 2024

mount_core

Modules Status Modules Status Modules Status Modules Status

Table of Contents

  1. Description
  2. Setup - The basics of getting started with mount_core
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hook peek at what the module is doing and how
  5. Development - Guide for contributing to the module

Description

The mount_core module manages mounted filesystems and mount tables. The module has some limitations, and you may be better off using the mount_providers module, which can manage mountpoints and mounttab resources independently.

Setup

What mount_core affects

The module can mount and unmount filesystems, and manage mount tables such as /etc/fstab, /etc/vfstab, or /etc/filesystems depending on your operating system.

Mount resources can respond to refresh events, and can remount a filesystem in response to an event from another resource.

Mount resources automatically create relationships with directories that are either ancestors of the mounted directory or children. This way Puppet will automatically create ancestor directories before the mount point, and will do that before managing directories and files within the mounted directory.

Usage

To mount the device /dev/foo at /mnt/foo as read-only, use the following code:

mount { '/mnt/foo':
  ensure  => 'mounted',
  device  => '/dev/foo',
  fstype  => 'ext3',
  options => 'ro',
}

Reference

Please see REFERENCE.md for the reference documentation.

This module is documented using Puppet Strings.

For a quick primer on how Strings works, please see this blog post or the README.md for Puppet Strings.

To generate documentation locally, run the following command:

bundle install
bundle exec puppet strings generate ./lib/**/*.rb

This command will create a browsable _index.html file in the doc directory. The references available here are all generated from YARD-style comments embedded in the code base. When any development happens on this module, the impacted documentation should also be updated.

Development

Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can't access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.

We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

For more information, see our module contribution guide.