Replies: 1 comment
-
| can you outline more succinctly: 
 i am no expert in go or the SDK, but it seems packages were organized into new logic units for user experience and better descriptors of the functionality. 🤷 | 
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey,
How can I mimic this functionally from v1 sdk?
I couldn't find any way to do that in v2, it looks like a lof ot the credentials logic is hidden, I don't have any controll on the chain order.
Now I need to use
LoadDefaultConfigwhich forcing the order of the providers.I could try to create a customer provider which chains providers together and try to
Retreivethem in order, however it means I need to write in hand providers likeSharedCredentialsProviderorEnvProviderwhich are not exist in v2.As a general feedback- I feel like there's a bit of mess in everything that related to the way we working with credentials in v2 sdk. Some logic belongs to
credentialspackage, some toawspackage (like theCredentialsstruct orCredentialsCache, like.. whyCredentialsCachelogic is not part ofcredentialspackage?), some toconfig.It was much easier to work with when everything was under
github.com/aws/aws-sdk-go/aws/credentialsBeta Was this translation helpful? Give feedback.
All reactions