Introduction

prancer is a cloud validation framework using for cloud governance

Use case scenarios

Multi cloud validation

you can use prancer to validate your post deployment configurations between two different clouds. Let’s say you have an AWS implementation for your application and you have configured the firewall to open certain ports. You have the same kind of application implemented in Azure and you want to make sure the same set of ports / rules are enabled on Azure Firewall as well. You can use prancer cloud validation framework to set up test cases to make sure rules are available and configured properly in a multi cloud environment.

workflow to validate resources in a multi cloud scenario

  • connect to the first cloud provider and take a snapshot of monitored resources
  • connect to all the other cloud providers and take snapshots of monitored resources
  • run the test cases to compare monitored resources within multi cloud environments
  • generate reports for passed / failed test cases

 

Cloud to git validation

you can use prancer cloud validation framework to post deployment validate your infrastructure in the cloud. Let’s say you are using an automation framework (like terraform) to provision resources in Microsoft Azure. Security team wants to make sure all the firewalls in the hub network are blocking port number 22. You can use the prancer cloud validation framework to run test cases against your cloud provider and generate a report for any compliance issue.

workflow to validate resources in the cloud

  • connect to your cloud provider and take a snapshot of monitored resources
  • connect to your git repository and read the parameter values of monitored resources
  • run the test cases to compare monitored resources from the cloud provider with the git repo
  • generate reports for passed / failed test cases


 

git to git validation

you can use prancer cloud validation framework to compare different configuration values between different git repositories. Usually enterprises use multiple automation frameworks and provisioning engines to deploy resources into the cloud. You can use prancer cloud validation framework to make sure you have the same set of configuration between these different automation frameworks and provisioning engines. For example, you can compare the rule sets of a firewall which is defined in the Azure ARM template to the rule sets that are available in the terraform code.

workflow to validate resources in the cloud

  • connect to your first git repository and read the parameter values of monitored resources
  • connect to all the other git repositories and read the parameter values of monitored resources
  • run the test cases to compare monitored resources from different git repos
  • generate reports for passed / failed test cases


 

Cloud configuration drifts

you can use prancer cloud validation framework to understand and measure configuration drifts in your cloud implementation. For example, you are using a cloud native firewall to control the access to your PaaS services in your cloud implementation. Each time prancer makes a snapshot, it stores the attributes of the firewall into database and you can see the changes you have made to this firewall over time to better understand the current situation.

workflow to validate resources in the cloud

  • connect to your cloud provider and take a snapshot of monitored resources
  • repeat the process multiple times over a period of time
  • generate reports for configuration drift


 

Document a cloud resource

you can use prancer validation framework to document the implementation that you have in your cloud environment. Let’s say you have used various tools and manual process to provision and update resources in your cloud provider. Now you want to document the current configuration to put it in a version control system or use it for an audit. You can use the prancer validation framework to connect to deployed resources in the cloud and document the resource in the json format.

workflow to document resources in the cloud

  • connect to your cloud provider and take a snapshot of monitored resources
  • generate the configuration report of the resource

Automated testing in CI/CD pipeline

You can use prancer cloud validation framework in your Continuous Integration (CI) / Continuous Deployment (CD) pipeline. Let’s say you have a build and release process for your Infrastructure as a Code (IaC) project and after each release to your test environment you want to make sure everything goes as planned. You can use prancer cloud validation framework API call to make a call to the framework from your CI/CD pipeline and after successfully pass all the tests, start the release process for your production environment.

workflow to integrate with CI/CD pipeline

  • make the API call to the prancer cloud validation framework
  • connect to your cloud provider and take a snapshot of monitored resources
  • connect to your git repository and read the parameter values of monitored resources
  • run the test cases to compare monitored resources from the cloud provider with the git repo
  • generate reports for passed / failed test cases
Suggest Edit