https://pulumi.com logo
Title
p

powerful-football-81694

12/18/2020, 2:28 PM
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.)
p

prehistoric-nail-50687

12/19/2020, 7:42 PM
and about the required password, this goes down to this: https://github.com/Azure/azure-rest-api-specs/issues/5029
p

powerful-football-81694

12/21/2020, 12:46 AM
@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.
👍 1
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. 👍 And their suggested workaround is what I ended up trying and that seems to work.
t

tall-librarian-49374

12/22/2020, 7:31 AM
Could you please open an issue for the Certificate error?
p

powerful-football-81694

12/22/2020, 1:42 PM
Yes @tall-librarian-49374 will do
@tall-librarian-49374 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?
t

tall-librarian-49374

03/07/2021, 3:32 PM
ouch. I do not know, that’s worrying… do you remember the title?
p

powerful-football-81694

03/07/2021, 3:35 PM
Unfortunately not, but it’s bound to be something containing the word “certificate”. And opened by DaRosenberg
t

tall-librarian-49374

03/07/2021, 3:36 PM
Thank you. That’s definitely not intended. We’ll try to revive it and see if other issues are missing.
p

powerful-football-81694

03/07/2021, 3:36 PM
No issues in the new repo (open or closed) are authored by me
OK, thx
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
t

tall-librarian-49374

03/10/2021, 7:54 PM
@powerful-football-81694 we recovered the issues now
p

powerful-football-81694

03/10/2021, 11:31 PM
Still can’t find this one though @tall-librarian-49374
t

tall-librarian-49374

03/11/2021, 7:29 AM
We haven’t moved closed issues
p

powerful-football-81694

03/11/2021, 6:10 PM
Ah ok