There's often confusion in where resources come from when using serverless (which creates CloudFormation stacks) vs other things support that like this process.
In the reference app, we have specific naming prefixes like:
"sls-${ServiceName}-${Stage}": In serverless.yml as service: value.
"aws-${ServiceName}-${Stage}": In AWS CloudFormation.
For our new project we should:
[ ] Support the variables ServiceName and Stage
[ ] Create a base Terraform name of "tf-${ServiceName}-${Stage}" to signal that these are Terraform managed.
[ ] Possibly also include the name of this project? (We could even give it a "cool", short name instead of the super boring serverless-iam-terraform)
[ ] Document this scheme.
[ ] In documentation, suggest users name their serverless app service"sls-${ServiceName}-${Stage}" with potentially an example.
There's often confusion in where resources come from when using serverless (which creates CloudFormation stacks) vs other things support that like this process.
In the reference app, we have specific naming prefixes like:
"sls-${ServiceName}-${Stage}": Inserverless.ymlasservice:value."aws-${ServiceName}-${Stage}": In AWS CloudFormation.For our new project we should:
ServiceNameandStage"tf-${ServiceName}-${Stage}"to signal that these are Terraform managed.serverless-iam-terraform)service"sls-${ServiceName}-${Stage}"with potentially an example.