You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am getting two warnings when managing a DHCP client interface using routeros_ip_dhcp_client:
Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
╷
│ Warning: Field 'primary_ntp' not found in the schema
│
│ with routeros_ip_dhcp_client.client,
│ on dhcp.tf line 1, in resource "routeros_ip_dhcp_client" "client":
│ 1: resource "routeros_ip_dhcp_client" "client" {
│
│ [MikrotikResourceDataToTerraform] The field was lost during the Schema development: ▷ 'primary_ntp': '216.239.35.0' ◁
╵
╷
│ Warning: Field 'secondary_ntp' not found in the schema
│
│ with routeros_ip_dhcp_client.client,
│ on dhcp.tf line 1, in resource "routeros_ip_dhcp_client" "client":
│ 1: resource "routeros_ip_dhcp_client" "client" {
│
│ [MikrotikResourceDataToTerraform] The field was lost during the Schema development: ▷ 'secondary_ntp': '216.239.35.4' ◁
╵
Releasing state lock. This may take a few moments...
To Reproduce
Import a routeros_ip_dhcp_client that has NTP peers.
Expected behavior
Warnings shouldn't happen. The primary_ntp and secondary_ntp should likely be in the schema as read-only parameters.
Stack Trace
None.
Additional context
The resource was imported using t import routeros_ip_dhcp_client.client "*2".
The text was updated successfully, but these errors were encountered:
Describe the bug
I am getting two warnings when managing a DHCP client interface using
routeros_ip_dhcp_client
:To Reproduce
routeros_ip_dhcp_client
that has NTP peers.Expected behavior
Warnings shouldn't happen. The
primary_ntp
andsecondary_ntp
should likely be in the schema as read-only parameters.Stack Trace
None.
Additional context
The resource was imported using
t import routeros_ip_dhcp_client.client "*2"
.The text was updated successfully, but these errors were encountered: