Open migara opened 2 years ago
Tasks:
Proposition of next steps regarding testing VM-Series modules for AWS:
tests
and stale
(besides this issue - #86)examples
and tests
change import
in order to use test skeleton for Terratest - replace github.com/PaloAltoNetworks/terraform-aws-vmseries-modules/go/testskeleton
by github.com/PaloAltoNetworks/terraform-modules-vmseries-tests-skeleton/pkg/testskeleton
go/testskeleton
and go/helpers
tests
, which contains integrations tests for modules:
terraform plan
(this kind of tests are going to be executed for PR CI) - now we don't have such tests for modules at all (only for examples we have it)vmseries
module we have tests:
TestOutputForModuleVmseriesWithFullVariables
, TestOutputForModuleVmseriesWithMinimumVariables
, TestOutputForModuleVmseriesWithS3BootstrappingAndFullVariables
. In order to shorten time of testing and limits cloud costs, maybe we should have only 2 kind of tests: TestModuleNNNPlan
, TestModuleNNNDeployment
.tests
e.g. for module nlb
tests
for PR CI (only plan) and for Release CI (with apply) - now we are not executing any Terratest from folder tests
, only from folder examples
, which for PR CI are only checking the plan, for Release CI are deploying all examples.After fulfilling all above steps we can start to think how to prepare E2E tests, in which we can configure VM-Series, deploy spokes VPCs and VMs and finally test traffic flows - inbound, outbound or east-west.
Summary
We will create Terratest test code to cover the below modules
VM-Series
Autoscaling
Panorama
ALB
NLB
VPC
create_vpc
set to falseTGW
create
set to falsecreate
set to falseGWLB