Skip to content

lkubb/salt-influxdb-formula

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

73 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

InfluxDB Formula

Semantic Release pre-commit

Manage InfluxDB with Salt.

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:

  • The Vault integration needs my custom Vault database plugin.
  • The Vault integration is setup statically, which means you need to create the required authorization manually and provide it to the formula. A complete bootstrap from scratch would be possible though.

An example pillar is provided, please see pillar.example. Note that you do not need to specify everything by pillar. Often, it's much easier and less resource-heavy to use the parameters/<grain>/<value>.yaml files for non-sensitive settings. The underlying logic is explained in map.jinja.

The following states are found in this formula:

Meta-state.

This installs the influxdb package, manages the influxdb configuration file and then starts the associated influxdb service.

Installs the influxdb package only.

This state will install the configured influxdb repository. This works for apt/dnf/yum/zypper-based distributions only by default.

Manages the influxdb service configuration. Has a dependency on influxdb.package.

Starts the influxdb service and enables it at boot time. Has a dependency on influxdb.config.

Meta-state.

Undoes everything performed in the influxdb meta-state in reverse order, i.e. stops the service, removes the configuration file and then uninstalls the package.

Removes the influxdb package. Has a dependency on influxdb.config.clean.

This state will remove the configured influxdb repository. This works for apt/dnf/yum/zypper-based distributions only by default.

Removes the configuration of the influxdb service and has a dependency on influxdb.service.clean.

Stops the influxdb service and disables it at boot time.

Commit messages

Commit message formatting is significant!

Please see How to contribute for more details.

pre-commit

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

State documentation

There is a script that semi-autodocuments available states: bin/slsdoc.

If a .sls file begins with a Jinja comment, it will dump that into the docs. It can be configured differently depending on the formula. See the script source code for details currently.

This means if you feel a state should be documented, make sure to write a comment explaining it.

Linux testing is done with kitchen-salt.

Requirements

  • 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.

bin/kitchen converge

Creates the docker instance and runs the influxdb main state, ready for testing.

bin/kitchen verify

Runs the inspec tests on the actual instance.

bin/kitchen destroy

Removes the docker instance.

bin/kitchen test

Runs all of the stages above in one go: i.e. destroy + converge + verify + destroy.

bin/kitchen login

Gives you SSH access to the instance for manual testing.