Remove implicit sequential dependency from typed action

[adam-cattermole]

DynamicTasks are treated as sequential implicitly rather than trusting the configuration to explicitly define dependence. Their onreply tasks also are tried to execute on response.. but then will enforce sequential ordering if requeued.

Once we migrate from legacy config we can remove the dependencies field entirely and have it explicitly defined.

Summary by CodeRabbit

Release Notes

• Bug Fixes
  • Improved action dependency handling in the pipeline compilation process for better execution flow and consistency between different action types.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f898e6c7-72e5-4cda-8568-2c761e89ddb0

📥 Commits

Reviewing files that changed from the base of the PR and between fd9455e and 9857fa6.

📒 Files selected for processing (1)

• src/kuadrant/pipeline/blueprint.rs

🚧 Files skipped from review as they are similar to previous changes (1)

• src/kuadrant/pipeline/blueprint.rs

---

📝 Walkthrough

Walkthrough

Blueprint::compile now assigns an empty dependencies vector to ActionConfig::Typed actions instead of the positional set derived from the preceding action. Action::compile_typed similarly compiles gRPC on_reply actions with an empty dependency list. A unit test assertion is updated accordingly.

Changes

Typed Action Dependency Isolation

Layer / File(s)	Summary
Empty dependency lists for typed actions and on_reply src/kuadrant/pipeline/blueprint.rs	Blueprint::compile branches on action kind: ActionConfig::Legacy retains positional dependency derivation, while ActionConfig::Typed receives []. Action::compile_typed removes the intra-reply dependency chain, compiling each gRPC on_reply action with an empty dependency vector.
Updated test assertion src/kuadrant/pipeline/blueprint.rs	mixed_legacy_and_typed_actions_compile changes the typed action's expected dependencies from vec!["0"] to is_empty().

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 No more chains for the typed brigade,
Each action stands free, no debt to be paid.
Legacy links still thread as before,
But typed ones now open their own fresh door.
Hop along, dependencies — you're off the hook!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Remove implicit sequential dependency from typed action' directly and specifically describes the main change: eliminating automatic dependency inheritance for typed actions, which is the core modification across the codebase.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch task-dependencies

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[adam-cattermole]

This keeps the dependencies between legacy types but not for the new types.. but dependencies should disappear once we burn Legacy