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

The idea of making these structs compatible makes sense, but this code is auto-generated from the Azure API spec. In that sense, we’re limited by their API design here.

Thank you for your answer. This is quite unfortunate to hear because that would mean we can't have a PrivateEndpointConnection to a PostgreSQL-Server and we can't have a Firewall-Rule for CosmosDB.

I can create these manually using the Web-UI, but I want to avoid this for sure :wink:

Do you see any other chance then trying the `azure-sdk-for-go` in this case?

So, I've found <https://learn.microsoft.com/en-us/rest/api/postgresqlhsc/firewall-rules/create-or-update?tabs=HTTP>

What would the derived pulumi resource be here? I can't find anything related at <https://www.pulumi.com/registry/packages/azure-native/api-docs/dbforpostgresql/> (but maybe I'm just blind here :smile: )

Hmm, if you can create these resources in the web portal and the Azure SDK, you should be able to create them using Pulumi, too. Except if something went wrong on our side when generating our SDK.

I see both <https://www.pulumi.com/registry/packages/azure-native/api-docs/dbforpostgresql/firewallrule/|FirewallRule> and <https://www.pulumi.com/registry/packages/azure-native/api-docs/dbforpostgresql/privateendpointconnection/|PrivateEndpointConnection> in the Pulumi registry. Are these not the right resources?

No, unfortunately the FirewallRule just works with the FlexibleServer and the PrivateEnpointConnection just works with the CosmosDB - see my first post.

To say it a bit more clear:

The <https://www.pulumi.com/registry/packages/azure-native/api-docs/dbforpostgresql/privateendpointconnection/#inputs|PrivateEndpointConnection> input just accepts a `Cluster` (CosmosDB). There is no way to define a `Server` (FlexibleServer)

The <https://www.pulumi.com/registry/packages/azure-native/api-docs/dbforpostgresql/firewallrule/#inputs|FirewallRule> input just accepts a `ServerName` (FlexibleServer). There is no way to define a `Cluster` (CosmosDB)

That's why I wrote It would be nice to have `ServerName` AND `ClusterName` in both structs.

I see, thanks for the explanation. This might be a bug on our side, I’m checking with some colleagues.

Just created the bug ticket <https://github.com/pulumi/pulumi-azure-native/issues/2753> to have notifications :slightly_smiling_face: Thanks for looking into it