First, thank you very much for this amazing work, I appreciate it a lot.
I have dns_challenge on all my hosts, this setting is read-only and I can't configure it before the first plan/apply, ok, no problem I will do that after, manually, so... next, in each plan/apply, this "meta" data is deleted.
This is the output when I try to plan each change, making this provider unusable when you have dns_challenge configured:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# nginxproxymanager_proxy_host.fog will be updated in-place
~ resource "nginxproxymanager_proxy_host" "fog" {
~ forward_host = "xxx.xxx.xxx.114" -> "xxx.xxx.xxx.14"
id = 56
~ meta = {
- "dns_challenge" = "true"
- "dns_provider" = "\"route53\""
- "dns_provider_credentials" = "\"[default]\\r\\naws_access_key_id=*****redacted******\\r\\naws_secret_access_key=**********redacted**********\""
- "letsencrypt_agree" = "true"
- "letsencrypt_email" = "\"*****redacted*****@**********.com\""
- "nginx_err" = "null"
- "nginx_online" = "true"
} -> (known after apply)
~ modified_on = "2024-02-29T17:07:43.000Z" -> (known after apply)
# (15 unchanged attributes hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
Obviously, when I try to configure it, I can't, the output is: "Cannot set value for this attribute as the provider has marked it as read-only. Remove the configuration line setting the value."
The question is, is there a way to tell to the provider do not touch this data, or is it really not read-only?
Please, if this a well known fact and there is no way to solve it, it'll a good idea to put a brief note advertising this behavior.
Thanks in advance.