And finally, fourth topic: there is an issue with the new provider when creating

Certificate

resources.

var certificate = new Pulumi.AzureNextGen.Web.V20190801.Certificate(
	$"orgflow-download-{stackName}-cert",
	new Pulumi.AzureNextGen.Web.V20190801.CertificateArgs()
	{
		Name = $"orgflow-download-{stackName}-cert",
		ResourceGroupName = resourceGroup.Name,
		Location = location,
		CanonicalName = publicHostname,
		ServerFarmId = appServicePlan.Id,
		Password = ""
	},
	new ResourceOptions()
	{
		// App Service Managed Certificates cannot be created unless a hostname binding has already
		// been added to the corresponding app service.
		DependsOn = hostnameBinding
	});

This creates an Azure-managed app service certificate for a web app. However,

pulumi up

fails on this resource with the following error:

azure-nextgen:web/v20190801:Certificate (orgflow-download-dev-cert):
  error: autorest/azure: error response cannot be parsed: "" error: EOF

Pulumi exits with a failure, and thinks the resource has not been created, but the certificate is actually created successfully in Azure. Next time we do

pulumi up

it fails because the resource is already there. So this one seems to be more of an issue with how Pulumi is handling a response from the API. (Also for some reason the

Password

property has to be set to something (it doesn’t matter what) which I think is a bug because for a managed certificate there are no passwords to worry about.)

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

@prehistoric-nail-50687 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.

Could you please open an issue for the Certificate error?

Yes @tall-librarian-49374 will do

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

@powerful-football-81694 we recovered the issues now

Still can’t find this one though @tall-librarian-49374

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

Ah ok