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

```def __createRole(self, role_name, password):


    role = postgresql.Role(
            f"{role_name}-rsc",
            name=role_name,
            login=True,
            password=password,
            opts=ResourceOptions(provider=self.postgresProvider),
        ),

    export("role", type(role))
    print(f"the type of role: {type(role)}")
    return (role_name, password, role)```


```  def __grantAccess(self, database_name, role_name, database, role):
        export(
            "grant",
            postgresql.Grant(
                f"table-grant-${role_name}-${database_name}",
                database=database_name,
                object_type="table",
                privileges=["SELECT", "DELETE", "INSERT", "UPDATE"],
                role=role_name,
                schema="public",
                opts=ResourceOptions(provider=self.postgresProvider, depends_on=[database, role]),
            ),
        )

        export(
            "grant",
            postgresql.Grant(
                f"db-grant-${role_name}-${database_name}",
                database=database_name,
                object_type="database",
                privileges=["CREATE", "CONNECT", "TEMPORARY"],
                role=role_name,
                schema="public",
                opts=ResourceOptions(provider=self.postgresProvider, depends_on=[database, role]),
            ),
        )```

Debugging, I print:    `the type of role: &lt;class 'tuple'&gt;`

I refactored to not output a tuple. But did the tuple transform the type (side effect?)

That refactoring fixed it?

I'm not a Python person, so am unfortunately not sure how that would affect the behavior.

It fixed it. I’m not sure if there was an editor cache issue or what. I might try to investigate again later.