terraform-provider-yandex
terraform-provider-yandex copied to clipboard
yandex-cloud
Terraform Yandex provider
It might sound not like terraform best practice, but having such thing would be pretty handy, i.e. if you have a lot of repos and would like to set lifecycle...
The following resource (from the [docs](https://registry.terraform.io/providers/yandex-cloud/yandex/latest/docs/resources/cm_certificate#example-usage-of-wildcard-managed-certificate)) ```hcl resource "yandex_cm_certificate" "ssl_cert" { name = "cert-example.com" domains = ["blah.example.com", "*.blah.example.com"] managed { challenge_type = "DNS_TXT" challenge_count = 1 } } ``` Fails...
The YC console shows something like this for a CDN resource: ``` $ORIGIN cdn.example.com CNAME cl-xxxx.edgecdn.ru ``` We need to have the same attribute available in TF to use it...
https://support.edgecenter.ru/knowledge_base/item/268821?sid=57227
Please add cleanup_policy for datatransfer_endpoint mysql_target
There is only the `source` param and no `type` or anything like that: ``` resource "yandex_cdn_origin_group" "my_group" { name = "My Origin group" origin { source = "mybucket" } }...
Hello, ``` ╷ │ Error: server-request-id = de46387e-7bea-4919-8d38-24bc7b6ff951 server-trace-id = 75372852026b4c29:b7732c6277122c98:75372852026b4c29:1 client-request-id = 7ebe6724-4e1f-474c-8467-c4dcc70afb8a client-trace-id = a5037f23-273f-4312-b368-cc051ee6945f rpc error: code = NotFound desc = Lifecycle policy with id crpqshjkrgkfiepe1qvt not...
Fix domains field in self_managed example doc │ Error: Conflicting configuration arguments │ │ with module.k8s.yandex_cm_certificate.alb, │ on modules/tf-yc-k8s-cluster/load_balancer.tf line 53, in resource "yandex_cm_certificate" "alb": │ 53: resource "yandex_cm_certificate" "alb"...
If you omit custom_host_header in resource definition any changes made with web console do not affect `terraform apply` - provider simply ignores it. Steps to reproduce: 1. create resource ```...
