There are several levels for dry-runs
- IaC (infrastructure as code)
I used terraform with option
plan, I can clearly see the resource changes before I deploy the change.
With this dry-run option (
terraform plan), I can check APIG, Lambda (not the code details, only setting about them), dynamodb tables, SQS/SNS or others.
I only check the configuration changes at this stage. In production, it shouldn’t change frequently, but I still need find a way to test a dry-run first.
sls deploy, or
sls deploy -noDeploy, I can’t have similar output for reference.
Think about this scenario, I set a CICD pipeline, I normally set these steps:
- deploy (or apply the change)
With every deployment, I need go through above steps, what should I put in first step (dry-run)
I will promote the deployment from dev, uat, then production. Even the changes are all fine in dev/uat, I still need a dry-run step before production deployment.
- Unit test (which mostly focus on labmda function codes).
I agree to run with mocha/chai or other testing tools.
- More, I am still looking for what should be put.