Proposal: Add typing for properties of known Resource types

[Woodz]

Currently the definition of Resources Properties is very generic:

        Properties?: {
          [k: string]: unknown;
        };

This does not provide support for or catch any issues with the properties of known resources. It looks like this is because the core serverless JsonSchema files do not cover known resources (because they don't need to), but it would be still be useful if this could be added into the TS definitions.

There is something similar in https://github.com/awslabs/goformation#updating-cloudformation--sam-resources-in-goformation (which uses the JSON schema from https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-resource-specification.html) which is then leveraged by https://github.com/threadheap/serverless-ide-vscode/tree/master/packages/cloudformation-schema to provide the VSCode plugin Serverless IDE that provides autocomplete for known Resource types when working in serverless.yml files as per https://github.com/threadheap/serverless-ide-vscode/tree/master/packages/cloudformation-schema.

I propose that a similar approach be taken where types are generated from the resource JSON schema published by AWS and these types be combined with the current definition of Resources to improve typing, i.e.

type KnownResource = AwsAppConfigEnvironment | AwsS3Bucket | ...

interface CustomResource {
        Type: string;
        Properties?: {
          [k: string]: unknown;
        };
}

type Resource = KnownResource | CustomResource;

[colesiegel]

Also looking for this

Was hoping this library would provide type support for the serverless deployment but it doesn't seem to have types for cloudformation resources.

[ebisbe]

I'm also interested in this feature.

[BrutalSimplicity]

https://github.com/bright/cloudform