Closed alastairs closed 3 years ago
Hey @alastairs thank you for reporting this. Is this somewhat the same issue as https://github.com/pulumi/pulumi-azure-native/issues/583 ?
Thanks for the swift response @mikhailshilkov. You're right I think, yes, it is the same - sorry for the duplicate ☺️
No worries. To be sure - when you say "Public DNS zones" - do you mean dns.RecordSet
or any other resource?
I'm only using RecordSet
from the network API at the moment, so just that one.
Closed as dupe of https://github.com/pulumi/pulumi-azure-native/issues/583
Following the announcement of the renaming of azure-nextgen to azure-native, I followed the migration steps outlined, and ran into two issues. I've attached a patchfile so you can see the changes involved in the migration.
Expected behavior
DNS zones can still be retrieved successfully.Current behavior
I now receive a "transport is closing" error message when retrieving my DNS zone withThis turned out to be a config problemazure-native@0.7.1
which I did not receive withazure-nextgen@0.6.1
.Steps to reproduce
I have a CustomHostname ComponentResource for creating all the necessary resources for an SSL-enabled custom hostname binding in Azure AppService, where the certificate lives in Azure Key Vault and the DNS zone is managed by Azure DNS: