Describe the feature
Relevant thread: https://github.com/awslabs/sbt-aws/pull/57/files/1276d286c6b568cdfaf25c17aaca6a739ad5039a#r1658784148
As I write this, one improvement that I think we need to make is to clarify to end-users what the value they should use for userId. This might require us to map the userName we get from a call such as admin_get_user(...) that we make as part of this function
|
def get_user(self, event): |
to userId and pass that back to the user. The result would be that the end-user sees userId wherever they would typically see userName and so we avoid confusion. That's something we can iron out, though. Appreciate the comment!
Use Case
This is to help customers avoid confusion between userName and userId.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.140.1
Environment details (OS name and version, etc.)
Mac OS
Describe the feature
Relevant thread: https://github.com/awslabs/sbt-aws/pull/57/files/1276d286c6b568cdfaf25c17aaca6a739ad5039a#r1658784148
Use Case
This is to help customers avoid confusion between
userNameanduserId.Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.140.1
Environment details (OS name and version, etc.)
Mac OS