acoustic-carpenter-78188
04/21/2026, 8:21 AMflyte run or flyte deploy with project that does not exists, we can successfully execute the runs and deploy tasks, but we can never see it on the UI as the project does not exists. We should block submitting runs / tasks to the project that does not exists.
What changes were proposed in this pull request?
In CreateUploadLocation, validate if the project exists before constructing signed url. If cannot find the project, raise "Not Found" error so flyte-sdk can raise it in CLI.
How was this patch tested?
Run flyte run and flyte deploy with project that does not exists. An error should be raise.
image
Labels
Please add one or more of the following labels to categorize your PR:
• added: For new features.
• changed: For changes in existing functionality.
• deprecated: For soon-to-be-removed features.
• removed: For features being removed.
• fixed: For any bug fixed.
• security: In case of vulnerabilities
This is important to improve the readability of release notes.
Setup process
Screenshots
Check all the applicable boxes
• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.
Related PRs
Docs link
• main
• #6583
• [V2] Dataproxy check project exists 👈
flyteorg/flyteacoustic-carpenter-78188
04/22/2026, 9:40 AM