mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #858] Different service check dialogs in agent vs automation manager #540
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#540
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @silversword411 on GitHub (Dec 12, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/858
Automation manager has:
Agent check only has:
@dinger1986 commented on GitHub (Dec 12, 2021):
Is that not ok though? It will show all the services it detects on that one machine (that it has access to)
@silversword411 commented on GitHub (Dec 12, 2021):
I wouldn't expect the dialogs to be different capabilities, should be consistent. If there's a reason they can close issue :)
@dinger1986 commented on GitHub (Dec 12, 2021):
I think it's worse being able to type it in on an agent. But yes happy leaving it up to the devs
@wh1te909 commented on GitHub (Dec 13, 2021):
yes this is intentional, agent service checks don't need an option to choose or enter manually because we already know what services are available on that agent. When creating a policy check, we don't know what agents it will apply to, so we have no way of knowing what services are available. Which is why the user needs to enter manually or choose from a list of defaults which is just some array we hardcoded with popular services.