The ip address database model has changed in Netbox 2.7.
Therefore the initializer code, that was used before, broke.
As a user, you will need to update your ip_addresses.yml
file as follows:
- Make sure the status is written in lower case.
See the diff of this commit for further information how this is meant.
The interface database model has changed in Netbox 2.7.
Therefore the initializer code, that was used before, broke.
As a user, you will need to update your dcim_interfaces.yml
file as follows:
- Make sure the type is a value out of the possible choices.
See the diff of this commit for further information how this is meant.
The vm database model has changed in Netbox 2.7.
Therefore the initializer code, that was used before, broke.
As a user, you will need to update your virtual_machines.yml
file as follows:
- Make sure the status is spelled lowercase.
See the diff of this commit for further information how this is meant.
The VLAN database model has changed in Netbox 2.7.
Therefore the initializer code, that was used before, broke.
As a user, you will need to update your vlans.yml file as follows:
- Make sure the status is spelled lowercase.
See the diff of this commit for further information how this is meant.
The device database model has changed in Netbox 2.7.
Therefore the initializer code, that was used before, broke.
As a user, you will need to update your devices.yml file as
follows:
- Make sure the rack face is spelled lowercase.
See the diff of this commit for further information how this is meant.
The rack database model has changed in Netbox 2.7.
Therefore the initializer code, that was used before, broke.
As a user, you will need to update your racks.yml file as follows:
- Rack types must match one of the 5 rack types given, e.g.
'4-post-cabinet'.
- Rack width must match one of the 2 rack widths given, i.e. '19' or
'23'.
See the diff of this commit for further information how this is meant.
The custom field database model has changed in Netbox 2.7.
Therefore the initializer code, that was used before, broke.
As a user, you will need to update your custom_fields.yml file as
follows:
- type must be lowercase
- the `selection` type was changed to `select`
- the filter_logic must be lower case
This is to achieve compatibility with the naming schema that
Netbox uses internally. It allows us to become forward compatible
in case Netbox ever introduces a new type for custom fields.
See the diff of this commit for further information how this is meant.
ryanmerolle
Christian Mäder
Eric Geldmacher
Aurélien Dunand
Les Begnaud
Jeroen Simonetti
Alvaro Arriola
Christian Mäder
Aleksandar Radunovic
thde