openldap

Table of Contents

• General notes
• Contributing to this repo
• Special notes
• Available states
  • openldap.client
  • openldap.server
• Testing
  • Requirements
  • bin/kitchen converge
  • bin/kitchen verify
  • bin/kitchen destroy
  • bin/kitchen test
  • bin/kitchen login

General notes

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.

Contributing to this repo

Commit message formatting is significant!!

Please see How to contribute for more details.

Special notes

None.

Available states

• openldap.client
• openldap.server

openldap.client

Install and configure ldap client. You should at least set pillar[openldap:base] and pillar[openldap:uri] to provide the client with minimal configuration.

openldap.server

Install and configure OpenLDAP-server slapd.

As for the client you should specify pillar[openldap:base]. The rootdn is set via pillar['openldap:rootdn'] (defaults to "cn=Manager," + pillar[openldap:base]), the rootpw via pillar[openldap:rootpw]. A hash for the later can be generated with slappasswd(8).

Testing

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