Predict deployment failures
Outputs warnings about potential deployment failures due to constraints in the account or misconfigurations in the template related to dependencies in the account.
NOTE: This is an experimental feature!
To use this command, add --experimental or -x as an argument.
This command is not a linter! Use cfn-lint for that. The forecast command is concerned with things that could go wrong during deployment, after the template has been checked to make sure it has a valid syntax.
This command checks for some common issues across all resources, and resource-specific checks. See the README for more details.
rain forecast --experimental <template> [stackName]
--action string The stack action to check: create, update, delete, all (default is all) (default "all")
-a, --all Show all checks, not just failed ones
-c, --config string YAML or JSON file to set tags and parameters
--debug Output debugging information
-x, --experimental Acknowledge that this is an experimental feature
-h, --help help for forecast
--ignore strings Resource types and specific codes to ignore, separated by commas, for example, AWS::S3::Bucket,F0002
--include-iam Include permissions checks, which can take a long time
--params strings set parameter values; use the format key1=value1,key2=value2
--plugin string Path to a forecast plugin .so
--plugin-only If set, none of the built in prediction functions will be run
-p, --profile string AWS profile name; read from the AWS CLI configuration file
-r, --region string AWS region to use
--role-arn string An optional execution role arn to use for predicting IAM failures
--tags strings add tags to the stack; use the format key1=value1,key2=value2
--type string Optional resource type to limit checks to only that type
--no-colour Disable colour output
- rain -