Apply security policy to flow endpoints

[MarceloRGonc]

Fixes OPS-3884.

[linear]

OPS-3884 Apply security policy to flow endpoints

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

This PR (Fixes OPS-3884) aims to apply the newer route security policy configuration to flow-related API endpoints so they can be governed via project-scoped security policies.

Changes:

• Added getProjectScopedRoutePolicy(...) to multiple flow endpoints to define project-scoped auth requirements.
• Updated flow and flow-version controller route configs to use the new config.security policy shape (including permissions/principal types).
• Minor formatting-only whitespace changes in the flow module.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
packages/server/api/src/app/flows/flow/flow.controller.ts	Adds project-scoped route security policies across multiple flow endpoints (create/update/list/count/get/delete/run).
packages/server/api/src/app/flows/flow/flow-version.controller.ts	Adds project-scoped route security policy to the “update trigger config” endpoint and updates another request options block.
packages/server/api/src/app/flows/flow.module.ts	Whitespace-only changes near websocket listener setup.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.