Ben Bernays

As of `v0.10.1` we are only missing the following resources: ``` aws_ec2_ebs_snapshots aws_ec2_eips aws_ec2_transit_gateway_attachments aws_ec2_transit_gateway_multicast_domains aws_ec2_transit_gateway_peering_attachments aws_ec2_transit_gateway_route_tables aws_ec2_transit_gateway_vpc_attachments aws_ecs_cluster_container_instances aws_iam_virtual_mfa_devices aws_route53_domains ```

All AWS resources that have an ARN should be implemented. Please open issues for any resources that you find that is missing an ARN field

Below is resource we are trying to deploy ``` AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Conditions: IsProdEnv: !Equals [!Ref "AWS::AccountId", ] Resources: CouponGeneration: Type: AWS::Serverless::Application Condition: IsProdEnv Properties: Location: ApplicationId: arn:aws:serverlessrepo:::applications/ SemanticVersion:...

I agree that the default behavior of that check failing should not cause fetch to stop. I also think it is important that users have a way of running CQ...

Initial improvements were merged in #1106 . Definitely more work to be done on the provider side of things

Can we add a validation command to the SDK so we can achieve the same results on all of the providers?

Add support for exclude field. Exclude should have a commented out list of all supported resources

Instead of appending we have decided to just support multiple config files

Create a `disable-log-redaction` flag. Ensure there is a huge warning to user about sensitive data in logs

@Hokwang - Thanks for the comment. I have opened a separate issue to track that request: #8261