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
Currently field choices appear to be validated against a hard coded list. It would be great if they could instead be validated against a list obtained from the netbox api. This would then support the use of custom field choices. I believe this can be obtained via the api as documented here
An example use case for this is for the IP Range resource. We have added a DHCP status choice, so we can document our DHCP pools. However we can't add these via terraform as the status validation currently fails.
Thanks!
The text was updated successfully, but these errors were encountered:
sirance
changed the title
Feature Request: Allow custom field choices
Feature Request: Allow custom status choices
Jan 25, 2024
Hi there,
Currently field choices appear to be validated against a hard coded list. It would be great if they could instead be validated against a list obtained from the netbox api. This would then support the use of custom field choices. I believe this can be obtained via the api as documented here
An example use case for this is for the IP Range resource. We have added a DHCP status choice, so we can document our DHCP pools. However we can't add these via terraform as the status validation currently fails.
Thanks!
The text was updated successfully, but these errors were encountered: