airship
/
deckhand
Code Issues Proposed changes
deckhand/deckhand/tests/integration
History
anthony.bellino 7defe473d2 Redact rendered Documents 
- Uses the rendered-documents endpoint
- Adds a query parameter ?cleartext-secrets
- Adds unit tests, updates integration tests

Change-Id: I02423b9bf7456008d707b3cd91edc4fc281fa5fc
 		2018-10-24 22:42:25 -04:00
..
gabbits Redact rendered Documents 2018-10-24 22:42:25 -04:00
README.rst Add integration tests 2018-04-18 09:05:04 -04:00
__init__.py Add integration tests 2018-04-18 09:05:04 -04:00

README.rst

Integration Tests

What

These tests validate integration scenarios between Deckhand, Keystone and Barbican. These scenarios include validating Deckhand's secret lifecycle management as well as substitution of encrypted secrets, which are stored in Barbican and retrieved by Deckhand during document rendering.

How

Deckhand uses gabbi to drive its integration tests. The entry point for these tests is integration-tests.sh under tools directory.

The integration environment is deployed using OpenStack-Helm which uses Helm to orchestrate deployment of Keystone, Barbican and other pre-requisite services.

Usage

These tests can be executed via ./tools/integration-tests.sh <test-regex> from the command line, where <test-regex> is optional and if omitted all available tests are run. sudo permissions are required. It is recommended that these tests be executed inside a VM as a lot of data is pulled in (which requires thorough clean up) during the deployment phase.