No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

is there a bug in aws 7.3 provider? i'm trying to use the following in my stack's .yaml:
```config:
  aws:assumeRole:
    roleArn: arn:aws:iam::&lt;accountid&gt;:role/some-role```
but it fails with `panic: interface conversion: interface {} is string, not []resource.PropertyValue`
downgrading to 6.83 works fine

I think this was one of the breaking changes in 7+. It is now `assumeRoles` with a collection to allow for role chaining.

ah, it's not what the docs say: <https://www.pulumi.com/registry/packages/aws/installation-configuration/#configuration-options>

<https://www.pulumi.com/registry/packages/aws/how-to-guides/7-0-migration/#provider-role-chaining>

probably the docs weren't updated to reflect this? I am not sure. I just know this because I am taking advantage of role chaining and was waiting for 7.x to land :smile:

Hey Ilya, this very much looks like a bug - can you please report this in <https://github.com/pulumi/pulumi-aws>

A program which reproduces the issue would be very valuable!

I ran into this issue too. I also try to upgrade from v6 to v7.

Can you try with

```config:
  aws:assumeRoles:
    - roleArn: arn:aws:iam::&lt;accountid&gt;:role/some-role```

When I update my config to the structure that Cory provided the `pulumi up --refresh --run-program` works again.

Thanks for confirming! I'll work on a fix so that we don't panic here and also update the docs to reflect the new types