Both preset mode and advanced (custom) mode in the deployment add-revision modal scope the model folder picker to the dedicated MODEL_STORE project. Add-revision flows pick a model folder from the user's accessible vfolders — not from the domain-wide model store — so the picker should follow the user's current project context.
Why This Work is Needed
The current implementation lists vfolders only from the MODEL_STORE project, which doesn't match the project the deployment lives in or the project the user is currently working from. This is inconsistent with the rest of the model-deployment UI (ServiceLauncherPageContent, ModelCardDeployModal) that already scopes vfolder pickers to the current project.
Expected Outcomes
- Both preset mode and advanced (custom) mode in
DeploymentAddRevisionModal show vfolders from the current project.
- Behavior matches existing model-deployment flows for consistency.
- Drop the now-dead
metadata.projectId field from the deployment query.
JIRA Issue: FR-2914
Both preset mode and advanced (custom) mode in the deployment add-revision modal scope the model folder picker to the dedicated MODEL_STORE project. Add-revision flows pick a model folder from the user's accessible vfolders — not from the domain-wide model store — so the picker should follow the user's current project context.
Why This Work is Needed
The current implementation lists vfolders only from the MODEL_STORE project, which doesn't match the project the deployment lives in or the project the user is currently working from. This is inconsistent with the rest of the model-deployment UI (
ServiceLauncherPageContent,ModelCardDeployModal) that already scopes vfolder pickers to the current project.Expected Outcomes
DeploymentAddRevisionModalshow vfolders from the current project.metadata.projectIdfield from the deployment query.JIRA Issue: FR-2914