-
Notifications
You must be signed in to change notification settings - Fork 640
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
suppress matching ipv6 dns record #3888
suppress matching ipv6 dns record #3888
Conversation
changelog detected ✅ |
thanks for the PR! can you ensure we add a regression test to cover this new functionality? |
@jacobbednarz I added the regression test for this case. I'm new to testing TF SDK v2 so please do let me know if there's something off here. I was unable to run the test locally, unfortunately. Here's my command:
and ran into this error
Do you notice anything wrong with my setup? I have double checked my key as well as the domain / zone ID. This is the same key that I used to manage my DNS records in my Terraform project, so it should have the right permission here I think. I used Proxyman to see which request it was making and I only saw 1 CONNECT request:
so I'm not sure where that error was coming from. I just saw the environment variables page so I updated my command but it still ran into the same error
|
that command looks right to me and i can run it locally. definitely make sure you don't have as for proxyman to check, you'll probably need to enable SSL proxying on the domain to ensure that you see more than the CONNECT requests. |
Hmm I don't believe there's any exported env. I'll double check and confirm again later. |
acceptance tests all passing
|
cheers for getting this one over the line 🚀 |
totally, and thanks for your support @jacobbednarz! |
As for the acceptance test, here's the 400 request:
response
Do you see anything wrong with by chance? Granted, the PR is already merged so we can move on too if you prefer to not spend too much time on it. We can certainly tackle it again in the off chance that I make another contribution later 😅 |
are you actually setting |
@jacobbednarz oops I was confused, I wasn't sure if I was supposed to use the exact value in the docs, sort of like a production mock, or if I should use my real credentials. I did try my credentials too but it still didn't work. I assume my API key is invalid. I tested my TF setup, it uses Alright so I digged a little deeper. Since I'm unfamiliar with Cloudflare API, I didn't know about the difference between API token & API key. Got myself the global API key and everything is good now. Thanks for your support! |
This functionality has been released in v4.41.0 of the Terraform Cloudflare Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Resolves #3864
Hi @jacobbednarz, here's the initial PR. I've gone over the contributing pages but there's a lot so please do let me know if there's anything else I should be adding. I'm also not sure if I should add a test here. I didn't see a unit test for record resource and wasn't sure how I can run acceptance safely. Would appreciate any guidance here.
I've built the provider and tested locally. It fixes my issue regarding IPv6.
Looking into the changelog thingy now.