Skip to content

saltstack-formulas/powerdns-formula

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

powerdns-formula

Travis CI Build Status Semantic Release

Installs a basic PowerDNS authorative server, and enables different backend configurations.

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 pay attention to the pillar.example file and/or Special notes section.

Commit message formatting is significant!!

Please see How to contribute for more details.

None

Installs PowerDNS authorative server.

Installs PowerDNS authorative server from official repostiory.

Installs PowerDNS LDAP backend package.

Installs PowerDNS MySQL backend package.

Installs PowerDNS sqlite3 backend package. Initializes sqlite3 db specified in config pillar.

Configures PowerDNS authorative server.

Installs the required pdnsapi python module. Requires pip to work.

To use this module, you need to have the following set either in pillar or your minion config:

pdns.url: "http://127.0.0.1:8081"
pdns.server_id: "localhost"
pdns.api_key: "deadbeef"

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