This message was deleted.

sparse-intern-71089

02/01/2024, 4:44 PM

This message was deleted.

clever-sunset-76585

02/02/2024, 2:38 AM

It's hard to give any insights (at least for me) from just that code. Your debug log will contain some sensitive info like your Azure subscription info, otherwise you could share it here. Sanitizing it is a bit hard. Having said that, the only pointers I can give is simplify your DB creation, i.e. remove private network etc. and just create the DB, destroy it and add features to it incrementally to see when the hangup starts. I assume this is a dev/test stack where you can destroy and recreate the DB temporarily till you figure out what's going on. Also, how are you authenticating to Azure?

az

CLI?

nutritious-leather-31262

02/02/2024, 10:34 AM

Hi @clever-sunset-76585 thank you for your interest. What you are suggesting was my next move I'll do as you advise. I'm authenticating using az cli indeed, but it's worth noting that I'm also creating other resources along with the DB and it's working well. The DB is the only thing at fault.

nutritious-leather-31262

02/02/2024, 10:41 AM

I'm also going to use azure classic instead of azure_native

nutritious-leather-31262

02/02/2024, 11:29 AM

Finally I have succeeded ! The issue was a typo in the administrator_login reference in my config file. I used the azure-classic provider and it returned the error right away. I'm going to open an issue for that since the azure-native provider should have prompted me the same way.

👍 1

clever-sunset-76585

02/02/2024, 12:53 PM

Awesome! Glad you are unblocked!

Open in Slack

Previous Next

Pulumi Community

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.