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
!!! warning
v1.0.0b3 introduces several database changes that are not backwards-compatible with v1.0.0b2 and earlier. There is no direct upgrade path from v1.0.0b2 to v1.0.0b3 - you must create a new database when installing v1.0.0b3!
Added
#100 - Added detailed documentation of the nautobot-server command
#105 - Added tooltip with detailed information to utilization graph bars.
#109 - Docker development environment build now automatically installs from any present local_requirements.txt file
#121 - Added "Data Model Changes" section to the "Migrating from NetBox" documentation
#141 - Custom Link UI now includes example usage hints
#227 - Add QFSP+ (64GFC) FiberChannel interface type
#236 - Add post_upgrade to developer docs and add invoke post-upgrade
Changed
Major backwards-incompatible database changes were included in this beta release that are intended are to pave the way for us to support MySQL as a database backend in a future update. Of those changes, these are the most notable:
All IPAM objects with network field types (ipam.Aggregate, ipam.IPAddress, and ipam.Prefix) are no longer hard-coded to use PostgreSQL-only inet or cidr field types and are now using a custom implementation leveraging SQL-standard varbinary field types
The users.User model has been completely replaced with a custom implementation that no longer requires the use of a secondary database table for storing user configuration.
Custom Fields have been overhauled for asserting data integrity and improving user experience
Custom Fields can no longer be renamed or have their type changed after they have been created.
Choices for Custom Fields are now stored as discrete database objects. Choices that are in active use cannot be deleted.
Other changes:
#78 - Replaced PostgreSQL-specific IP network/address fields with more generic field types
#83 - Custom user model added; UserConfig model merged into User model
#84 - Revised developer documentation for clarity and current workflows
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
v1.0.0b3 (2021-04-05)
!!! warning
v1.0.0b3 introduces several database changes that are not backwards-compatible with v1.0.0b2 and earlier. There is no direct upgrade path from v1.0.0b2 to v1.0.0b3 - you must create a new database when installing v1.0.0b3!
Added
nautobot-server
commandlocal_requirements.txt
filepost_upgrade
to developer docs and addinvoke post-upgrade
Changed
Major backwards-incompatible database changes were included in this beta release that are intended are to pave the way for us to support MySQL as a database backend in a future update. Of those changes, these are the most notable:
ipam.Aggregate
,ipam.IPAddress
, andipam.Prefix
) are no longer hard-coded to use PostgreSQL-onlyinet
orcidr
field types and are now using a custom implementation leveraging SQL-standardvarbinary
field typesusers.User
model has been completely replaced with a custom implementation that no longer requires the use of a secondary database table for storing user configuration.Other changes:
nautobot-netbox-importer
plugin could be mistaken for full instructionsREMOTE_AUTH*/SOCIAL_AUTH*
$PATH
contrib.postgres.fields.JSONField
fordb.models.JSONField
Removed
RQ_DEFAULT_TIMEOUT
CSRF_TRUSTED_ORIGINS
from core settingssettings.BASE_PATH
Fixed
nautobot-server runserver
does not work usingpoetry run
nautobot_config.py
did not include a trailing newlineAUTHENTICATION_BACKENDS
example in remote authentication documentationedit_uri
to point to correct pathThis discussion was created from the release Release v1.0.0b3 - 2021-04-05.
Beta Was this translation helpful? Give feedback.
All reactions