Add related object context to Zabbix tag and hostgroup templates

[taofineberg]

Add related object context to Zabbix tag and hostgroup templates

Summary

Add related NetBox object context to templated Zabbix tags and hostgroups.

Previously, templates only had access to the assigned object through object, plus the tag or hostgroup fields. This change exposes common related objects directly in the Jinja2 context when available.

What Changed

This PR adds the following template variables for Zabbix tag and hostgroup templates:

• device
• site
• tenant
• role
• device_type
• manufacturer

This allows templates such as:

{{ site.name }}
{{ device.name }}
{{ device_type.model }}
{{ manufacturer.name }}

Why

This makes Zabbix tag and hostgroup templates easier to write and more flexible.

For example, users can now build dynamic tag or hostgroup values from related NetBox data without having to access everything indirectly through object.

Implementation

• Updated ZabbixTagAssignment.get_context() to include related object context.
• Updated ZabbixHostgroupAssignment.get_context() to include related object context.
• Added tests for the new context variables.
• Added render tests confirming templates can use related fields.

Testing

• git diff --check passed.
• ruff was not run because it is not installed in this container.
• Django tests were not run from this checkout because there is no local manage.py in /opt/nbxsync.

[bvbaekel]

Hey @taofineberg,

Thanks for taking the time to work on this: exposing related object context directly in the Jinja2 templates is a great quality-of-life improvement. Really appreciate the initiative.

I do have a few things that need to be addressed before we can merge this:

Bug: manufacturer lookup crashes on VMs and Virtual Device Contexts
The manufacturer check (hasattr(self.assigned_object.device_type, 'manufacturer')) sits outside the device_type guard. Since assigned_object can be a VirtualMachine or Virtual Device Context, neither of which has a device_type attribute: this line will raise an AttributeError. It needs to be nested inside the if hasattr(..., 'device_type') block. Both model files have this issue.

Unrelated commits in the PR
The branch includes the v1.0.4 release commit and version bump (5a4beca, 0ca97e0) which are unrelated to this feature. Could you rebase onto development so the PR only contains your feature commit (656e07d)? This keeps the history clean and makes review easier.

device alias assumes Device objects only
Hardcoding 'device': self.assigned_object means the context will have a device key even when the assigned object is a VM or Virtual Device Context. This could be confusing for users. Consider either omitting the alias, or making it conditional on the actual object type.

Documentation
The new template variables (site, tenant, role, device_type, manufacturer) need to be documented so users know they're available. A brief addition to the relevant docs section covering the available context variables and a usage example would be sufficient.

The feature itself is solid and something users have been asking for. Once these items are addressed we should be good to go.

Happy to help if you have questions on any of these points.

Thanks again!