stscreds/assume_role_provider usage documentation is incorrect

[brodie-slater]

Describe the issue with documentation
When using the stscreds.NewAssumeRoleProvider for the first time, I looked at the examples in the source code which, at time of writing shows:

cfg, err := config.LoadDefaultConfig(context.TODO())
	if err != nil {
		log.Fatal(err)
	}

stsSvc := sts.NewFromConfig(cfg)
creds := stscreds.NewAssumeRoleProvider(stsSvc, "myRoleArn")

cfg.Credentials = &aws.CredentialsCache{Provider: creds}
}

The issue is that, using cfg.Credentials = &aws.CredentialsCache{Provider: creds} doesn't compile. aws.CredentialsCache doesn't export the field Provider. If it once did, it is now a private field used by aws.NewCredentialsCache.

To Reproduce (observed behavior)
Follow the example code in the source file here

Expected behavior
A working example of how to use stscreds.NewAssumeRoleProvider

Additional information
I was able to get my program working with:

cfg, err := config.LoadDefaultConfig(context.TODO())
if err != nil {
	log.Fatal(err)
}

stsSvc := sts.NewFromConfig(cfg)
creds := stscreds.NewAssumeRoleProvider(stsSvc, "myRoleArn")

cfg.Credentials = creds << assigning creds directly

I didn't want to raise a PR suggesting this as a fix because I'm not sure if this is the best way to do it, or if it's better to use a CredentialsCache in some way.

Sorry if this sounds nitpicky. Thanks for all the work on this SDK, I love using it ❤️

[skmcgrail]

Thank you for bringing this to our attention @brodie-slater, this is an example we missed updating before we released the SDK for general availability. We will put together a PR to get this example fixed up.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.