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

please see: <https://github.com/pulumi/pulumi-azure-nextgen/issues/129>

and about the required password, this goes down to this: <https://github.com/Azure/azure-rest-api-specs/issues/5029>

<@U01EPRHN6HF> That’s a different issue. The circular dependency problem I know about from before, and I have a solution for that by using a TemplateDeployment to do the final update of the host name binding to enable it for SSL.

The problem here happens earlier, while creating the certificate.

As I said, it does get created successfully but Pulumi thinks it’s not.

On the required password, yep that issue is spot-on. :thumbsup:  And their suggested workaround is what I ended up trying and that seems to work.

Could you please open an issue for the Certificate error?

<https://github.com/pulumi/pulumi-azure-nextgen/issues/212>

<@UB39JFCKC> trying to track the status of this issue, but it seems to not have been migrated to the new pulumi-azure-native repo. Can you advice on what happened with it?

ouch. I do not know, that’s worrying… do you remember the title?

Unfortunately not, but it’s bound to be something containing the word “certificate”. And opened by DaRosenberg

Thank you. That’s definitely not intended. We’ll try to revive it and see if other issues are missing.

No issues in the new repo (open or closed) are authored by me

I remember you mentioned in the issue you were putting in a workaround for this one

Something to do with Azure returning an unexpected status code

Still can’t find this one though <@UB39JFCKC>

<https://github.com/pulumi/pulumi-azure-nextgen/issues/212> works for me