Hello,

Do you plan to support Terraform scans with OpenStack in the future ?

Regards

https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html lists the maximum environment variable hard limit as 4kb.

If this limit is exceeded, the template will not deploy.

It should be possible to make an Error level rule around this

While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f

Add error handling during credentials onChange event so that the Scan Account feature does not activate if credentials are invalid

Good summary at https://matthewdf10.medium.com/how-to-enable-logging-on-every-aws-service-in-existence-circa-2021-5b9105b87c9 and https://docs.google.com/spreadsheets/d/1DBmCXX1irJvxdewa85p5nSsYEf3tpSKWBbwp700mbzs/edit#gid=0

Amazon Aurora
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html#cfn-rds-dbcluster-enablecloudwatchlogsexports

AWS AppSync

Describe the bug

CodeUri in Function has invalid directory name

To Reproduce

• Create a powershell package using the new-awsPowerShellLambdaPackage:

New-AWSPowerShellLambdaPackage -ScriptPath checkdomainavailable.ps1 -OutputPackage checkdomainavailable.zip

• Add the function in template.yaml

CheckDomainAvailableFunction:
Type: AWS::Serverless::Function
Pr

Seems like we can encrypt environment variables effectively for free by adding a KmsKeyArn property to functions. See: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md

This would be an easy contribution for a first timer...

Pretty simple cfn-guard test -r rules.txt -t test.yaml will pass and exit with 0 if test.yaml doesn't exist.

The current behavior of --interactive is that any new stacks will get created, without any prompt. But this can be potentially dangerous (or at the very least, annoying) if you accidentally make a change, like changing the stack name, resulting in a whole new stack getting created.

Should stacker prompt you before creating a stack when using --interactive mode?