feat: sweeper should change managed device setting #813

Open
opened 2026-03-28 04:28:48 +00:00 by mfreeman451 · 0 comments
Owner

Imported from GitHub.

Original GitHub issue: #2423
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2423
Original created: 2026-01-21T06:05:12Z


Is your feature request related to a problem?

If a user configures a network sweep and we discover a device, that device should automatically be marked 'Managed' unless it is already explicitly set to false. In other words, if a user adds a new device, it shouldn't necessarily be marked managed or unmanaged, its just unset. If this works in elixir, this would allow us to safely mark untouched devices, but also not overwrite ones that were explicitly set to unmanaged. If this doesn't work, we might just have to add an additional 'activated' field or something.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Imported from GitHub. Original GitHub issue: #2423 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2423 Original created: 2026-01-21T06:05:12Z --- **Is your feature request related to a problem?** If a user configures a network sweep and we discover a device, that device should automatically be marked 'Managed' unless it is already explicitly set to false. In other words, if a user adds a new device, it shouldn't necessarily be marked managed or unmanaged, its just unset. If this works in elixir, this would allow us to safely mark untouched devices, but also not overwrite ones that were explicitly set to unmanaged. If this doesn't work, we might just have to add an additional 'activated' field or something. **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar#813
No description provided.