pulumi up --debug -v=9 --logflow --logtostderr --yes --skip-preview
to get the raw HTTP requests and responses. Maybe you’d spot what goes wrong.
a
able-doctor-68496
06/21/2021, 8:27 PM
That's exactly what I was hoping for - I'll give that a try
able-doctor-68496
06/21/2021, 8:41 PM
Indeed, that revealed the error coming back from Azure:
The Cname record cannot point at the same resource record.
Now I just need to figure out what that means.
able-doctor-68496
06/21/2021, 8:56 PM
Looks like I forgot that I want the CNAME record to point to my Kubernetes service... So that makes sense.
t
tall-librarian-49374
06/22/2021, 10:23 AM
Awesome that you found the error. If you don’t mind, could you open an issue describing that a useful error message was lost and attach obfuscated HTTP logs? That would be super helpful.
No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.