feat(serviceCatalog): support agentic workflow blueprints (QOV-2181)

[fabienfleureau]

Summary

Adds support for agentic workflow blueprints in the service catalog (Jira QOV-2181).

Agentic workflow blueprints are cloud-agnostic — they are not tied to a specific cloud provider. The catalog's isBlueprintCompatibleWithCluster filter only surfaces a blueprint when its provider matches the cluster's cloud provider or the provider is on the cloud-agnostic allow-list (EXTERNAL, HELM). As a result, agentic workflow blueprints were hidden on any cluster bound to a specific cloud (AWS/GCP/SCW/…).

This change adds AGENTIC_WORKFLOW to CLUSTER_AGNOSTIC_BLUEPRINT_PROVIDERS, so these blueprints are offered on any cluster — mirroring the existing EXTERNAL/HELM handling introduced in #2895.

Files changed

• libs/domains/services/feature/src/lib/blueprint-utils/blueprint-utils.ts — add AGENTIC_WORKFLOW to the cloud-agnostic provider allow-list.
• libs/domains/services/feature/src/lib/blueprint-utils/blueprint-utils.spec.ts — add the matching it.each row.

Verification

⚠️ No JS toolchain (node/yarn) was available in the execution environment, so yarn test / lint / typecheck could not be run here. The change was verified by inspection:

• isBlueprintCompatibleWithCluster('AGENTIC_WORKFLOW', 'AWS') now returns true via the allow-list; other providers are unaffected.
• A parametrized test row was added to lock in the behavior; please let CI run the suite.

Assumptions

• The blueprint provider token for agentic workflows is AGENTIC_WORKFLOW, consistent with ServiceTypeEnum.AGENTIC_WORKFLOW and the Icon name="AGENTIC_WORKFLOW" usage across the console. The comparison is case-insensitive (.toUpperCase()), so any casing of agentic_workflow matches. Please confirm the exact provider string used in the Qovery/service-catalog catalog.json — if it is hyphenated (agentic-workflow) the allow-list entry must be adjusted. If the token differs, this change is a safe no-op (nothing else is affected).

Follow-ups

• Confirm the provider token against Qovery/service-catalog and, if needed, publish the actual agentic workflow blueprint entries there.
• Dedicated card presentation / deploy routing for agentic workflow blueprints (e.g. routing "Deploy" to the agentic-workflow creation flow) likely requires a service-type/kind field on BlueprintItem from the generated qovery-typescript-axios API — out of scope for this minimal change.

Jira

https://qovery.atlassian.net/browse/QOV-2181

---

Summary by cubic

Shows agentic workflow blueprints on all clusters by treating AGENTIC_WORKFLOW as cloud-agnostic. Previously these blueprints were hidden on cloud-bound clusters; now they appear regardless of provider, matching EXTERNAL/HELM.

• Adds AGENTIC_WORKFLOW to CLUSTER_AGNOSTIC_BLUEPRINT_PROVIDERS in blueprint-utils.ts; other providers unchanged.
• Extends isBlueprintCompatibleWithCluster test to cover AGENTIC_WORKFLOW.
• Action: Confirm the service catalog provider token is AGENTIC_WORKFLOW; adjust the allow-list entry if the token differs.

^{Written for commit 0d14756. Summary will update on new commits.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 0d14756

Command	Status	Duration	Result
nx run console:build --parallel=3 --configurati...	✅ Succeeded	58s	View ↗
nx affected --target=test --parallel=3 --config...	✅ Succeeded	2m 35s	View ↗
nx affected --target=lint --parallel=3	✅ Succeeded	3m 8s	View ↗
nx-cloud record -- yarn nx format:check	✅ Succeeded	5s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-08-24 10:08:49 UTC

[Copilot]

Pull request overview

This PR updates the service catalog blueprint compatibility filter to treat agentic workflow blueprints as cluster/cloud-agnostic, so they appear on clusters regardless of the cluster’s cloud provider (matching existing EXTERNAL / HELM behavior).

Changes:

• Add AGENTIC_WORKFLOW to the CLUSTER_AGNOSTIC_BLUEPRINT_PROVIDERS allow-list used by isBlueprintCompatibleWithCluster.
• Extend the unit test matrix to assert the new compatibility behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
libs/domains/services/feature/src/lib/blueprint-utils/blueprint-utils.ts	Adds AGENTIC_WORKFLOW to the cluster-agnostic provider allow-list used by the compatibility check.
libs/domains/services/feature/src/lib/blueprint-utils/blueprint-utils.spec.ts	Adds a parametrized test row ensuring AGENTIC_WORKFLOW is compatible with an AWS cluster.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.76%. Comparing base (720181b) to head (0d14756).

Additional details and impacted files

@@             Coverage Diff             @@
##           staging    #2898      +/-   ##
===========================================
- Coverage    49.29%   44.76%   -4.53%     
===========================================
  Files          849      489     -360     
  Lines        21194    13025    -8169     
  Branches      6443     4017    -2426     
===========================================
- Hits         10448     5831    -4617     
+ Misses        8932     6164    -2768     
+ Partials      1814     1030     -784     

Flag	Coverage Δ
unittests	44.76% <100.00%> (-4.53%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.