Hi All, I'm testing out the upgrade from Pulumi.A...
# azure
f
Hi All, I'm testing out the upgrade from Pulumi.AzureNative v2.9 to 3.0, and have run into an unexpected issue. When deploying to our dev environment, I get the following error: error: Status=400 Code="CertificateInUse" Message="Certificate 'cert-zzzzzzz is used by existing custom domains." What's weird is that none of the code we changed as part of the upgrades affects certs... but I suspect it did change the ContainerApp namespace in the pulumi state file, which is causing a "Refresh" update in the Pulumi run. Before I go deleting the cert and it's binding in our ingress app, is there something else I might have missed here? We have many, many deployments this will affect, and deleting the binding and the cert and letting it try to recreate these will require taking our production sites down. Not ideal. Would I be better off to manually edit the state file? (Insert fear emoji here)
Copy code
~ azure-native:app/v20231102preview:Certificate: (refresh)
          [id=/subscriptions/zzzz/resourceGroups/zzzzz/providers/Microsoft.App/managedEnvironments/cae-zzz/certificates/cert-zzzzzzz]
          [urn=urn:pulumi:zzzzz::CustomerInstance::azure-native:app/v20231102preview:Certificate::cert-zzzzzzz]
          [provider=urn:pulumi:zzzzz::CustomerInstance::pulumi:providers:azure-native::zzzzz-azure-provider::fa2165a6-a041-445b-a1af-46260a4d9a66]
t
Oh! Recreating certificates can't be the only option, there is always a way around. Do you mind opening an issue in azure-native and describing the exact flow of operations that you are running? Your snippet shows a refresh but the error sounds like it's coming from an update?
f
I created the following issue: Certificate in Use Error after upgrade from AzureNative 2.9 to 3.0 · Issue #4139 · pulumi/pulumi-azure-native Unfortunately the real expert we had in Pulumi left the company last month, and I'm trying to pick up the pieces and keep things running. Let me know if there is something basic I have missed in making this update.
s
Did anything ever come of this errror ? We are getting it as well while rotating our certificates...