Skip to content

Feature: Add Site/SiteGroup/Region to ConfigGroupAssignment form#116

Open
berlikm wants to merge 6 commits into
OpensourceICTSolutions:developmentfrom
berlikm:feature/configgroup-site-form
Open

Feature: Add Site/SiteGroup/Region to ConfigGroupAssignment form#116
berlikm wants to merge 6 commits into
OpensourceICTSolutions:developmentfrom
berlikm:feature/configgroup-site-form

Conversation

@berlikm

@berlikm berlikm commented Jul 13, 2026

Copy link
Copy Markdown

Summary

Adds Site, SiteGroup, and Region to the ZabbixConfigurationGroupAssignment form's assigned object target choices, so ConfigGroup interface templates can be assigned at the country/site-group level.

Dependencies

Stacks on PR #115. Merge after #115.

Testing

All existing tests pass.

Part of #121.

berlikm added 3 commits July 14, 2026 14:15
Adds Site, SiteGroup, and Region as valid assignment targets for all
ZabbixServerAssignment, ZabbixHostgroupAssignment, ZabbixTemplateAssignment,
ZabbixTagAssignment, ZabbixMacroAssignment, and ZabbixHostInventory objects.

This allows assignments made at the Site/SiteGroup/Region level to be
inherited by all devices and VMs at that site or below, via the existing
inheritance_chain mechanism.

Changes:
- Constants: Site/SiteGroup/Region added to ASSIGNMENT_MODELS, ASSIGNMENT_TYPE_TO_FIELD, PATH_LABELS
- Forms: All 7 assignment forms get Site/SiteGroup/Region DynamicModelChoiceField + FieldSet
- Settings: inheritance_chain extended with Site/SiteGroup/Region resolution paths
- Jobs: SyncHostJob._prepare_assignment() creates detached copies for inherited assignments
- HostSync: _get_sync_target() resolves actual Device/VM for Jinja2 rendering
- HostSync: get_tag_attributes() deduplicates tags by (tag, value) to prevent
  Zabbix 7 rejecting duplicate pairs inherited from multiple sources
- HostInterfaceSync: get_create_params() falls back to the device's primary IP
  when the interface has no IP assigned (e.g. when inherited from SiteGroup)
- HostInterfaceSync: errors are caught per-interface so one failing interface
  does not prevent the remaining interfaces and templates from being synced
- Inheritance: ConfigGroup interface expansion removed; interfaces are now
  resolved naturally via the inheritance chain with primary IP fallback
- SyncBase: _is_inherited_copy guard prevents save()/update_sync_info() on inherited copies
- Views: ZabbixSiteTabView, ZabbixSiteGroupTabView, ZabbixRegionTabView added
- Tests: 9 new tests for inheritance resolution

Tested: all 1076 existing tests pass. Verified end-to-end on dev NetBox.
- Filter inherited/direct ZabbixServerAssignment and ZabbixHostInterface by zabbixserver
- Resolve ConfigGroup interface IP from primary_ip4/primary_ip6
- Add seen-set cycle guard to resolve_path
- Fixes silent dropping of Site/SiteGroup assignments
@berlikm
berlikm force-pushed the feature/configgroup-site-form branch from ccda6df to 09afa8d Compare July 14, 2026 14:34
berlikm added 2 commits July 14, 2026 14:54
Fixes inherited Site/SiteGroup/Region assignments reading custom fields from
the intermediate object instead of the actual Device/VM.
… in minimal.html

- zabbixconfigurationgroupassignment.py: Add Site, SiteGroup, Region as
  DynamicModelChoiceField with FieldSet tabs and Meta.fields entries.
  Matches the pattern used by the other 6 assignment forms.
- minimal.html: Add '+Add' buttons for Host Inventory and Configuration Group
  in the Miscellaneous panel. When no assignment exists, users see a blue
  Add button instead of just '-'. Links pre-fill assigned_object_type/id.
@berlikm

berlikm commented Jul 14, 2026

Copy link
Copy Markdown
Author

This PR is part of the zero-touch provisioning feature set described in #121. Please see that issue for the full architecture and motivation.

berlikm added a commit to berlikm/nbxsync that referenced this pull request Jul 15, 2026
…gets

# Conflicts:
#	nbxsync/forms/zabbixconfigurationgroupassignment.py
Adds ZabbixSyncBase._should_persist() returning False for transient
inherited copies (those carrying _is_inherited_copy). Replaces the 4
inline getattr reads in syncbase.py and the 1 read in hostsync.py
(_clear_direct_hostid / verify_hostinterfaces) with the helper call.

Centralizes the persistence guard so a future change to the inherited-copy
mechanism touches one method, not nine call sites. The model-level guard
in sync_info.py:25 stays as the backstop.

Adds two test_syncbase cases: _is_inherited_copy=True skips save() and
update_sync_info(); absent/False runs them as before.
@berlikm
berlikm force-pushed the feature/configgroup-site-form branch from 0ef0028 to fbbc591 Compare July 16, 2026 07:33
@berlikm

berlikm commented Jul 16, 2026

Copy link
Copy Markdown
Author

Conflict resolution note for rebase

When rebasing this PR after #115 lands, there will be a conflict in nbxsync/utils/sync/syncbase.py:

Correct resolution: Take this PR's version (_should_persist()). This commit (fbbc591) centralizes the _is_inherited_copy check behind _should_persist() — it's the more evolved version. The method is defined in this PR and is already used by the else branch in #115's base.

Verified in the integration-test branch: 1135 tests pass, E2E confirmed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant