-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pulumi up/preview hangs for DNS record #903
Comments
Thank you for filing this issue, @the-gigi. I will verify with the team that the Java SDK has the same behavior as the other Pulumi languages. We'll take a look - thank you for providing us with your code, and for trying multiple provider versions as well. |
@guineveresaenger Update: I managed to create a new DNS record when the name of the record include the domain:
In the end instead of importing into Pulumi, I had to delete the original DNS record and re-create it using Pulumi. Anyway, even if the import is corrupted or using invalid name without the domain, it shouldn't hang. |
@the-gigi - glad you found a resolution. I agree that hanging is a bad experience. We are working on validating inputs for our users, so I'll keep this issue open to track this. |
Describe what happened
When running
pulumi up
it hangs forever when it needs to create or update aDNS record
. It works fine with aZone
.I also tried to import an existing DNS record and got this message:
Is the Java flavor of the Cloudflare provider fully supported? DNS records is arguably the primary Cloudflare resource. Looking at the Github issues I see only two Java issues (one closed and one open).
Please advise how to fix or troubleshoot this problem.
Sample program
Here is a sample code, very similar to the example program
Log output
The logs are empty.
Affected Resource(s)
DNS records not created.
Output of
pulumi about
Additional context
I'm on the latest version 3.58.0. I tried with the previous version too (3.57.0) with the same results.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: