Configure automounting with pam-mount.
Table of Contents
See the full SaltStack Formulas installation and usage instructions.
If you are interested in writing or contributing to formulas, please pay attention to the Writing Formula Section.
If you want to use this formula, please pay attention to the FORMULA file and/or git tag,
which contains the currently released version. This formula is versioned according to Semantic Versioning.
See Formula Versioning Section for more details.
If you need (non-default) configuration, please refer to:
- how to configure the formula with map.jinja
- the
pillar.examplefile - the Special notes section
Commit message formatting is significant!!
Please see How to contribute for more details.
pre-commit is configured for this formula, which you may optionally use to ease the steps involved in submitting your changes.
First install the pre-commit package manager using the appropriate method, then run bin/install-hooks and
now pre-commit will run automatically on each git commit.
$ bin/install-hooks pre-commit installed at .git/hooks/pre-commit pre-commit installed at .git/hooks/commit-msg
None
Meta-state (This is a state that includes other states).
This installs the required packages and manages the pam-mount configuration file.
It depends on:
Meta-state (This is a state that includes other states).
Managage packages required to use pam-mount.
This state will install the pam-mount package and the declared dependencies.
This state will configure pam_mount.conf.xml for the declared volumes.
It depends on:
Meta-state (This is a state that includes other states).
This state will undo everything performed in the pam-mount meta-state in reverse order, i.e. removes the configuration file and then uninstalls the packages.
It depends on:
This state will remove the pam-mount configuration file.
This state will remove the pam-mount package.
It depends on:
Linux testing is done with kitchen-salt.
- Ruby
- Docker
$ gem install bundler
$ bundle install
$ bin/kitchen test [platform]Where [platform] is the platform name defined in kitchen.yml,
e.g. debian-9-2019-2-py3.
Creates the docker instance and runs the pam-mount main state, ready for testing.
Runs the inspec tests on the actual instance.
Removes the docker instance.
Runs all of the stages above in one go: i.e. destroy + converge + verify + destroy.
Gives you SSH access to the instance for manual testing.