dvirlabs 1cbe3d4de7 fix: Use checksum-based content comparison to avoid permission-based drift false positives ...

CRITICAL FIX:

Problem: drift-check.yml was using 'copy' module in check_mode, which compares:
  - File content ✓
  - Permissions (owner, group, mode) ✗
  - Ownership ✗

After deploy, files have root:root 0644 permissions. Even though content matches,
the copy module marked files as 'changed' because permissions were being compared.
This caused false OUT_OF_SYNC reports even when configuration was actually synced.

Solution: Use MD5 checksum-based comparison instead:
  - Compare only file CONTENT using stat checksums
  - Ignore permissions/ownership differences
  - This is what matters for config management

Also fixed URLs:
  - Changed back from port 80 to port 5000 (API only)
  - Updated service name to gitops-status-api

Now drift detection only triggers on actual config changes, not permission differences.
After successful deploy, should correctly report SYNCED status.

2026-04-23 13:21:20 +03:00

..

inventory

test

2026-04-17 17:07:29 +03:00

playbooks

fix: Use checksum-based content comparison to avoid permission-based drift false positives

2026-04-23 13:21:20 +03:00