Open dhoffend opened 3 months ago
This is not as trivial as it seems at first, I'm afraid.
I see two options to implement this:
pk
of the referenced nat_inside
address object (unambiguous, but not very user-friendly)address
of the referenced nat_inside
address object (might be ambiguous or even wrong in some cases, e.g. if there is an object with the specified address
, but not in the correct VRF).Any ideas on how to best solve this? I'm afraid the only safe implementation is the one using pk
.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.
NetBox version
v4.0.5
Feature type
New functionality
Proposed functionality
Allow nat ip address fields in the bulk import dialog.
Use case
We're trying to migrate a bigger number of ip addresses with static nat translations into the netbox. The current bulk csv import header fields don't allow those fields to be imported.
Database changes
No response
External dependencies
No response