sbt-aws should define the name of the email field so downstream services know where to get that attribute within the tenant object.
Use Case
Email is an important attribute for a tenant object to have as it is often required by downstream services and 3rd party plugins. If sbt-aws does not standardize it, we risk each end-user defining it on their own making it difficult for downstream services to consume that field in a uniform manner.
Proposed Solution
No response
Other Information
No response
Acknowledgements
[ ] I may be able to implement this feature request
Describe the feature
sbt-aws should define the name of the email field so downstream services know where to get that attribute within the tenant object.
Use Case
Email is an important attribute for a tenant object to have as it is often required by downstream services and 3rd party plugins. If sbt-aws does not standardize it, we risk each end-user defining it on their own making it difficult for downstream services to consume that field in a uniform manner.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.133.0
Environment details (OS name and version, etc.)
Mac OS