AWSCredentialIdentityResolver currently requires that the developer import SmithyIdentity. There is benefit in encouraging developers to write code that's flexible about credential identity resolvers, both for current utility but also to better support future credential identity provider types that may be added.
Use Case
I'm writing library code that wants to accept input parameters of type any AWSCredentialIdentityResolver, so the program can use any credential identity resolver type from the same function.
Proposed Solution
Since we are trying to avoid requiring developers to import any of the Smithy modules directly, we should add a typealias for this type in AWSSDKIdentity.
Other Information
No response
Acknowledgements
[ ] I may be able to implement this feature request
Describe the feature
AWSCredentialIdentityResolvercurrently requires that the developerimport SmithyIdentity. There is benefit in encouraging developers to write code that's flexible about credential identity resolvers, both for current utility but also to better support future credential identity provider types that may be added.Use Case
I'm writing library code that wants to accept input parameters of type
any AWSCredentialIdentityResolver, so the program can use any credential identity resolver type from the same function.Proposed Solution
Since we are trying to avoid requiring developers to import any of the Smithy modules directly, we should add a
typealiasfor this type inAWSSDKIdentity.Other Information
No response
Acknowledgements