Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UA: ensure the pending behavior is still correct #23921

Open
mna opened this issue Nov 18, 2024 · 0 comments
Open

UA: ensure the pending behavior is still correct #23921

mna opened this issue Nov 18, 2024 · 0 comments
Labels
~backend Backend-related issue. #g-mdm MDM product group :product Product Design department (shows up on 🦢 Drafting board) ~sub-task A technical sub-task that is part of a story. (Not QA'd. Not estimated.)

Comments

@mna
Copy link
Member

mna commented Nov 18, 2024

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:

@mna 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~backend Backend-related issue. #g-mdm MDM product group :product Product Design department (shows up on 🦢 Drafting board) ~sub-task A technical sub-task that is part of a story. (Not QA'd. Not estimated.)
Development

No branches or pull requests

1 participant