Skip to content

Releases: lae/ansible-role-netbox

v1.0.7

05 Jul 13:08
@lae lae
2858bd2
Compare
Choose a tag to compare

What's Changed

  • User get_user_model() rather than importing User directly by @sleinen in #180
  • NetBox 4.0.0 and higher requires Python 3.10 or higher by @sleinen in #178
  • Adding Amazon Linux 2023 support by @melonger in #181
  • add reindex command for 3.4.5+ by @tyler-8 in #186

New Contributors

Full Changelog: v1.0.6...v1.0.7

v1.0.6

29 Feb 21:10
@lae lae
b1f4673
Compare
Choose a tag to compare

What's Changed

  • Add task to overwrite package dependencies by @bbe-dw in #169

New Contributors

Full Changelog: v1.0.5...v1.0.6

v1.0.5

26 Feb 04:51
@lae lae
dc9538f
Compare
Choose a tag to compare

Update Notes

  • Debian 12 (bookworm) is now supported.
  • netbox_rqworker_processes role variable can now be used to increase request queue worker count.
  • Setting netbox_uwsgi_in_venv to true will install uwsgi in NetBox' venv. This is the default on Debian 12, and may become the default on all distros in the future.

What's Changed

New Contributors

Full Changelog: v1.0.4...v1.0.5

v1.0.4

05 May 15:20
@lae lae
efca97d
Compare
Choose a tag to compare

Maintenance release/NetBox 3.0.12 update

2.11.0's major changes: https://github.com/netbox-community/netbox/releases/tag/v2.11.0
3.0.0's major changes: https://github.com/netbox-community/netbox/releases/tag/v3.0.0

#140 Added support for Debian 11
#147 Added support for Ubuntu 22.04
#149 Added support for RHEL9
#141, #142, #153 NetBox 3.0 updates
#158 Introduce netbox_database_maintenance role variable for specifying a different database for Ansible to initially connect to.

v1.0.3

31 Oct 22:51
@lae lae
99d3dca
Compare
Choose a tag to compare

NetBox 2.10.10 release

https://github.com/netbox-community/netbox/releases/tag/v2.10.10

#135 Fix for netbox_processes when Ansible doesn't detect number of CPU cores
#122 Ensure netbox user can read and execute uwsgi
#133 Introduce role variables for configuring Redis Sentinel (Redis HA)
#111 Add netbox_database_options role variable for extra options for Postgres
#128 (+ 9a30774) Add netbox_superuser_enabled and netbox_superuser_create_token role variables for enabling/disabling superuser and generating an API token for it.

v1.0.2

11 Nov 17:29
@lae lae
6eb842a
Compare
Choose a tag to compare

v1.0.1

05 Nov 09:09
@lae lae
8ecf6b4
Compare
Choose a tag to compare

NetBox 2.9.8 release (support for any 2.9.x version).

Note: Using NetBox 2.9.x requires your Redis instance to be v4.0 or later.

https://github.com/netbox-community/netbox/releases/tag/v2.9.8

#114 Replace DEFAULT_TIMEOUT by RQ_DEFAULT_TIMEOUT
#115 Backwards compatibility for older NetBox versions and some bug fixes with regards to that.

v1.0.0

02 Nov 14:14
@lae lae
6278325
Compare
Choose a tag to compare

NetBox 2.8.9 release

https://github.com/netbox-community/netbox/releases/tag/v2.8.9

#91 Add support for Ubuntu 20.04 (Focal)
#106 Clean up ansible-lint and yamllint issues
#108 Fixes this role to properly run via include_role

v1.0.0rc2

22 Jun 18:11
@lae lae
09df22a
Compare
Choose a tag to compare

NetBox 2.8.6 release

https://github.com/netbox-community/netbox/releases/tag/v2.8.6

84300e0 django-rq 2.3.1 is blacklisted, which fixes an UnpickleError issue. See #93 for info.
#102 Bug fix for Prometheus metrics feature

v1.0.0rc1

06 May 15:50
@lae lae
bcab5ba
Compare
Choose a tag to compare

NetBox 2.8.1 release

https://github.com/netbox-community/netbox/releases/tag/v2.8.1

ebcf10e netbox_pip_packages role variable introduced for installing extra dependencies for a NetBox deployment. You can use this role variable to specify NetBox plugins, dependencies for your scripts, etc.
83e3a40 Python 3.6+ is required when deploying NetBox 2.8+. (Support for older NetBox versions (2.7.12 being the latest) is still retained, however.)
#90 CentOS 8 targets are now supported.
#89 Fixed bug where ansible_python_interpreter was not reset to its previous value.
#93 Fixed deprecation issue in Redis config

There're a couple doc updates (see open issues) and some other stuff I want to get through before marking a 1.0 release, but it may take a while, so I'm tagging this in advance. Deploying this version should totally be fine.