Skip to content

Commit 4991b05

Browse files
committed
feat: authoritative plugin fields
Signed-off-by: jokob-sk <jokob.sk@gmail.com>
1 parent 8ea84a2 commit 4991b05

File tree

3 files changed

+7
-13
lines changed

3 files changed

+7
-13
lines changed

docs/API_DEVICE_FIELD_LOCK.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -138,12 +138,6 @@ The Device Edit form displays lock/unlock buttons for all tracked fields:
138138
2. **Unlock Button** (🔓): Click to allow plugin overwrites again
139139
3. **Source Indicator**: Shows current field source (USER, LOCKED, NEWDEV, or plugin name)
140140

141-
### Source Indicator Colors
142-
143-
- Red (USER): Field was manually edited by a user
144-
- Orange (LOCKED): Field is locked and protected from overwrites
145-
- Gray (NEWDEV/Plugin): Field value came from automatic discovery
146-
147141
## UI Workflow
148142

149143
### Locking a Field via UI

docs/QUICK_REFERENCE_FIELD_LOCK.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ The device field lock/unlock system allows you to protect specific device fields
66

77
**Use case:** You've manually corrected a device name or port number and want to keep it that way, even when plugins discover different values.
88

9-
## Tracked Fields (10 Total)
9+
## Tracked Fields
1010

1111
These are the ONLY fields that can be locked:
1212

@@ -97,7 +97,7 @@ Each locked field has a "source" indicator that shows you why the value is prote
9797

9898
## Quick Tips
9999

100-
- **Lock names and IPs you manually corrected** to keep them stable
100+
- **Lock names you manually corrected** to keep them stable
101101
- **Leave discovery fields (vendor, FQDN) unlocked** for automatic updates
102102
- **Use locks sparingly**—they prevent automatic data enrichment
103103
- **Check the source indicator** (colored badge) to understand field origin
@@ -133,7 +133,7 @@ Each locked field has a "source" indicator that shows you why the value is prote
133133
- Double-check the lock icon shows
134134
- Reload the page—the change might be a display issue
135135
- Check if you accidentally unlocked it
136-
- pen an issue if it persists
136+
- Open an issue if it persists
137137

138138
## For More Information
139139

server/scan/session_events.py

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,12 +56,12 @@ def process_scan(db):
5656
mylog("verbose", "[Process Scan] Updating Devices Info")
5757
update_devices_data_from_scan(db)
5858

59-
# Last Connection Time stamp from CurrentSan
60-
mylog("verbose", "[Process Scan] Updating devLastConnection from CurrentSan")
59+
# Last Connection Time stamp from CurrentScan
60+
mylog("verbose", "[Process Scan] Updating devLastConnection from CurrentScan")
6161
update_devLastConnection_from_CurrentScan(db)
6262

63-
# Presence from CurrentSan
64-
mylog("verbose", "[Process Scan] Updating Devices Info")
63+
# Presence from CurrentScan
64+
mylog("verbose", "[Process Scan] Updating Presence from CurrentScan")
6565
update_presence_from_CurrentScan(db)
6666

6767
# Update devPresentLastScan based on NICs presence

0 commit comments

Comments
 (0)