Introduction

prancer is a cloud validation framework using for cloud governance

Terms

Monitored Resource
A resource which is important for us to monitor. This resource could be in the cloud, or in a parameter file.

Connector
Prancer can use various “connector”s to connect to cloud providers and git repositories. Each connector has a special configuration file to be able to be used in the framework.

Snapshot
By using various connectors, you can connect to a cloud provider and make a snapshot of a monitored resource. By doing this, based on the available information from the provider, all the attributes will be captured and stored in the database. You can make snapshots overtime and store attributes of the monitored resource overtime. All of these attributes will be stored in the database with the appropriate timestamp.

Test
Prancer uses a powerful comparison engine to run test cases against the monitored resources. You can check for the availability of a resource, or any attributes which is exposed by the corresponding API. Everytime you run the test, prancer will make a new snapshot based on the defined connectors, and do the comparison of the attribute values.

Report
Prancer generates an output for every test file based on each run. All the test cases available in a test file will be evaluated and a Passed/Failed reports will be generated. This report can be used to further investigate the failed cases.

Container
a container consists of snapshot file(s) and test file(s). you can run all the tests in a container at once by a single command

structure file
The structure file is a json file which define the connectivity to a provider. For example if you want to connect to a cloud provider, you need to create a structure file for that connection.

Comparison
There are various operators and operands available for the comparison of test cases in the prancer.

Suggest Edit