powerful-football-81694
12/18/2020, 2:28 PMCertificate
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.)prehistoric-nail-50687
12/19/2020, 7:42 PMpowerful-football-81694
12/21/2020, 12:46 AMtall-librarian-49374
12/22/2020, 7:31 AMpowerful-football-81694
12/22/2020, 1:42 PMtall-librarian-49374
03/07/2021, 3:32 PMpowerful-football-81694
03/07/2021, 3:35 PMtall-librarian-49374
03/07/2021, 3:36 PMpowerful-football-81694
03/07/2021, 3:36 PMtall-librarian-49374
03/10/2021, 7:54 PMpowerful-football-81694
03/10/2021, 11:31 PMtall-librarian-49374
03/11/2021, 7:29 AMpowerful-football-81694
03/11/2021, 6:10 PM