-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
google_dns_record_set - type "DS" is not expected type #8897
google_dns_record_set - type "DS" is not expected type #8897
Comments
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp/terraform-provider-google#8897
I opened GoogleCloudPlatform/magic-modules#4689 which should fix this. Looks like it's just an incomplete whitelist in the magic modules service spec. |
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp/terraform-provider-google#8897
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp/terraform-provider-google#8897 Signed-off-by: Modular Magician <magic-modules@google.com>
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp/terraform-provider-google#8897 Signed-off-by: Modular Magician <magic-modules@google.com>
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp/terraform-provider-google#8897 Signed-off-by: Modular Magician <magic-modules@google.com>
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp/terraform-provider-google#8897 Signed-off-by: Modular Magician <magic-modules@google.com>
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp#8897 Signed-off-by: Modular Magician <magic-modules@google.com>
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp/terraform-provider-google#8897 Signed-off-by: Modular Magician <magic-modules@google.com>
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes #8897 Signed-off-by: Modular Magician <magic-modules@google.com>
Update the list of valid DNS record types to match the list documented at https://cloud.google.com/dns/docs/records. In particular this was hurting people who were previously deploying DNSSEC key records via terraform. Closes hashicorp/terraform-provider-google#8897 Signed-off-by: Modular Magician <magic-modules@google.com>
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
The expected behavior from "terraform validate" should pass. "DS" is a valid DNS record type (reference doc)
Actual Behavior
Steps to Reproduce
terraform validate
Important Factoids
We downgraded the provider to use version 3.63.0 rather than using the latest version (3.64.0).
References
The text was updated successfully, but these errors were encountered: