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

Hi, we've just found out that DigitalOcean schema does have a problem with clashing field names - there are fields called `urn` in their schema which clash with Pulumi's URN. Who maintains this provider? Example: <https://www.pulumi.com/registry/packages/digitalocean/api-docs/reservedip/#urn_nodejs> in 4.22.0 <@UCWG26BH7>?

it looks like it's enough to replace:

`"digitalocean_reserved_ip":            {Tok: makeResource(digitalOceanMod, "ReservedIp")},`
with this:
```"digitalocean_reserved_ip":            {
                Tok: makeResource(digitalOceanMod, "ReservedIp"),
				Fields: map[string]*tfbridge.SchemaInfo{
					"urn": {
						Name: "reservedIpUrn",
					},
				},  
},```
here:
<https://github.com/pulumi/pulumi-digitalocean/blob/3e72e24b04dcc05956f7970bc1123142025aaa0b/provider/resources.go#L293>

I've opened a PR that might fix this: <https://github.com/pulumi/pulumi-digitalocean/pull/515>

seems that flaky test completed successfully after a rerun, when could this be merged and the schema rebuilt? we can build DO without ReservedIp class for now but a complete fix in schema would be nice :)