You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
~backendBackend-related issue.#g-mdmMDM product group:productProduct Design department (shows up on 🦢 Drafting board)~sub-taskA technical sub-task that is part of a story. (Not QA'd. Not estimated.)
Prior to the unified queue, the pending upcoming activities were all stored in their "final" tables - e.g. nano_commands, host_script_results, etc. but with some NULL column indicating that the actual result was pending. Some fleet behavior depended on that - e.g. summaries of host counts by state, deletion of pending script execution when a script is modified, etc.
We need to ensure those "pending state" behaviors are adjusted to work properly in the new unified queue world.
Most (possibly all?) of those places where the "pending" state depended on the upcoming activity to be in its final table were captured in the brainstorm document:
The text was updated successfully, but these errors were encountered:
mna
added
:product
Product Design department (shows up on 🦢 Drafting board)
~backend
Backend-related issue.
#g-mdm
MDM product group
~sub-task
A technical sub-task that is part of a story. (Not QA'd. Not estimated.)
labels
Nov 18, 2024
~backendBackend-related issue.#g-mdmMDM product group:productProduct Design department (shows up on 🦢 Drafting board)~sub-taskA technical sub-task that is part of a story. (Not QA'd. Not estimated.)
Prior to the unified queue, the pending upcoming activities were all stored in their "final" tables - e.g.
nano_commands
,host_script_results
, etc. but with some NULL column indicating that the actual result was pending. Some fleet behavior depended on that - e.g. summaries of host counts by state, deletion of pending script execution when a script is modified, etc.We need to ensure those "pending state" behaviors are adjusted to work properly in the new unified queue world.
Most (possibly all?) of those places where the "pending" state depended on the upcoming activity to be in its final table were captured in the brainstorm document:
The text was updated successfully, but these errors were encountered: