Skip to content
This repository has been archived by the owner on Jan 8, 2021. It is now read-only.

Releases: synackray/vcenter-netbox-sync

v1.1.0 - 2020-16-02

15 Feb 23:40
dbb8a85
Compare
Choose a tag to compare

Note: This is a major release and has new dependencies. Please make sure to run pip install -r requirements.txt when upgrading from a previous version and update your settings.py based on the latest settings.example.py.

Enhancements

  • Handle changes to API in NetBox v2.7.0 #25
  • Generic banned asset tags are not accounting for word case #31
  • Add already exist esxi-hosts in netbox to cluster object in netbox #37
  • Query DNS for PTR lookups and populate dns_name field for IP address objects #42
  • Support unique credentials per vCenter host #43
  • Add primary_ip by default #46
  • Allow placement of synced devices in cabinets #49
  • Improve handling of serial numbers and asset tags #58

Bug Fixes

  • Netbox virtual interfaces do not support tag filter #33
  • Link speed detection can cause backtrace #38
  • Requests with bad status code generate traceback #41
  • NetBox formatting rules not applied to object relationships #45
  • Handle value changes in NetBox API v2.7 #50
  • Cleanup tasks fail for IP defined vCenter hosts #51

Please report any issues in the issues tracker. Thank you for your support!

v1.0.0 - 2020-07-01

07 Jan 13:43
8e15612
Compare
Choose a tag to compare

v1.0.0 - 2020-07-01

Please enjoy the first production release of vCenter NetBox Sync! Thanks for the testing and feedback.

Bug Fixes

  • Pruning generates traceback on interface objects #24

Enhancements

  • Allow for sync with NetBox if it contains an untrusted cert #27

Please report any issues in the issues tracker. Thank you for your support!

v1.0.0-rc.3 - 2020-01-01

01 Jan 14:49
c046761
Compare
Choose a tag to compare
Pre-release

v1.0.0-rc.3 - 2019-30-12

Bug Fixes

  • vCenter Hosts defined by IP are not tagged properly #21

Please report any issues in the issues tracker. Thank you for your support!

v1.0.0-rc.2 - 2019-30-12

30 Dec 22:18
f55e885
Compare
Choose a tag to compare
Pre-release

v1.0.0-rc.2 - 2019-30-12

Notice

If you have used a previous release it is recommended you first wipe the current vCenter objects by executing run.py --cleanup. Once you have completed the cleanup operation you can safely upgrade. The reason for this is noted in the Enhancement sections.

Bug Fixes

  • Cleanup function fails when multiple vCenter instances have overlapping parents #8
  • Orphaned objects are not having tags removed #14
  • HTTP POST error when having Model number with nonsupported symbols #16
  • vCenter host tag is inaccurate if an IP address is used #18

Enhancements

  • As part of #18 a review of all Netbox data models was done to ensure object value compliance. New functions and parsing has been added to ensure compliance to NetBox's rules. This may affect existing objects if they were previously out of compliance.

Please report any issues in the issues tracker. Thank you for your support!

v1.0.0-rc.1 - 2019-28-12

28 Dec 18:40
fc3da89
Compare
Choose a tag to compare
Pre-release

v1.0.0-rc.1 - 2019-28-12

Bug Fixes

  • Device types in more than one vCenter instance change tags on every run #1
  • Traceback error when collecting information on disconnected vCenter host #3
  • Cluster Type "VMware ESXi" not found #4

Please report any issues in the issues tracker. Thank you for your support!

v1.0.0-rc - 2019-25-12

27 Dec 12:02
Compare
Choose a tag to compare
Pre-release

v1.0.0-rc - 2019-25-12

Enhancements

  • Removed secondary vCenter entry in settings.example.py to avoid confusion
  • Cleaned up code to closer adhere to PEP-8
  • Added project license

Bug Fixes

  • Prefix search was using the wrong filter paramater in query
  • NetBox virtual interfaces do not support filtering by tags

Please report any issues in the issues tracker. Thank you for your support!

v1.0.0-beta - 2019-25-12

26 Dec 14:54
Compare
Choose a tag to compare
Pre-release

v1.0.0-beta

Beta Release

All core functionality documented in the project board has been implemented. All initial QA tests have passed. The project is ready for additional community testing prior to production release.

Please report any issues in the issues tracker. Thank you for your support!