This message was deleted.

There's no provider for this, but

Pulumi.Command

has been presented as an option for this sort of thing in the past.

Is there any guidance on best practice for

Pulumi.Command

in cases like this? Ex: Would it make sense to actively set the MSSQL database as Parent resource in this case, or would DependsOn=MyDataBaseResource be sufficient?

As I understand them: • The Parent controls both the dependency resolution and the location of the resource in the stack's tree • DependsOn only links the two resources for dependency resolution I think Parent therefore places stronger restrictions on deployment ordering than DependsOn. DependsOn is probably sufficient, in this scenario, but Parent better conveys the container->object relationship IMO.

The problem is not to create a workaround, but suggestion to implement this functionality. Therefore where should it be posted or who should be mentioned?

As best I can tell, Pulumi don't take requests to implement new providers, but will accept new providers once implemented (and might offer some support in implementing them too). There's a sort of "getting started" document here. If there's a Terraform provider for SQL Server already, then you can get a leg up implementing one for Pulumi using the pulumi-terraform-bridge. You might also find some inspiration in the MySQL and PostgreSQL providers.

I wish it was on C#😅