saltstack-formulas/packages-formula
1
0
Fork 0
mirror of https://github.com/saltstack-formulas/packages-formula.git synced 2025-04-17 10:10:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
A simple 'packages manager' formula, to install/remove packages without further ado.
8 commits 3 branches 16 tags 644 KiB
Find a file
Javier Bértoli d02d4b807c Add reload_modules: true to pip.installed (closes #3)
2018-02-21 07:10:25 -03:00
packages Add reload_modules: true to pip.installed (closes #3) 2018-02-21 07:10:25 -03:00
test/integration/default Initial commit 2018-02-15 11:23:05 -03:00
.gitignore Initial commit 2018-02-15 11:23:05 -03:00
.kitchen.yml Fix debian image name for testing 2018-02-15 14:03:18 -03:00
.travis.yml Add some travis caching 2018-02-15 15:02:09 -03:00
CHANGELOG.rst Initial commit 2018-02-15 11:23:05 -03:00
Gemfile Add travis support 2018-02-15 13:16:29 -03:00
LICENSE Initial commit 2018-02-05 21:20:46 -03:00
pillar.example Initial commit 2018-02-15 11:23:05 -03:00
README.rst Documentation fixes 2018-02-15 19:23:38 -03:00

README.rst

packages-formula

A simple 'packages manager' formula, to install/remove packages without further ado.

image

What this formula can do

Many times, in the process of setting up a host/vm, you need to install/remove packages with no extra configuration or setup. This formula tries to help with that. It can get a list of packages from a pillar, and it will try to install them.

It provides a few states to install/remove system packages (currently Debian/Redhat families), Python packages (using pip states) and Ruby gems (using gem states).

It can also provide basic dependency management on certain other states/packages.

What this formula can't do

This formula is not intended to configure packages, nor setup services or daemons. When you need to do that for a package, you should probably be using another formula.

Available states

packages --=---------

Runs all the other states in the formula.

packages.pkgs

You can specify:

  • wanted system packages, which will be installed.
  • unwanted system packages, which will be uninstalled.
  • required system packages on which any of the wanted packages depend for their correct installation.
  • required states on which any of the wanted packages depend for their correct installation.

packages.pips

You can specify:

  • wanted python packages, which will be installed using pip. Requires you specify the correct python-pip package for your distro, as a dependency (see the pillar.example)
  • unwanted python packages, which will be uninstalled using pip.
  • required system packages on which any of the wanted python packages depend for their correct installation. Usually, a python-pip package and/or some other compiler packages are required.
  • required states on which any of the wanted packages depend for their correct installation (ie, epel for RedHat families).

packages.gems

You can specify:

  • wanted ruby packages, which will be installed using gem. Requires you specify the correct ruby package for your distro, as a dependency (see the pillar.example)
  • unwanted ruby packages, which will be uninstalled using gem.
  • required system packages on which any of the wanted ruby packages depend for their correct installation. Usually, a ruby package and/or some other compiler packages are required.
  • required states on which any of the wanted packages depend for their correct installation (ie, epel for RedHat families).

packages.remote_pkgs

You can specify a dictionary of remote system packages (deb/rpm) that you want to install, in the format:

name: url

Testing

Testing is done with Test Kitchen for machine setup and inspec for integration tests.

Tested on

  • Debian/9
  • Centos/7
  • Ubuntu/17.10