Partial deployment (-m): reduce upload overhead and improve dependency error messages

未关闭
#1,944 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
backend

调研方向

Start by tracing the controller's partial deployment handling for module selection and dependency validation; the issue does not name specific files or tests. Check how the selected module and resources are packaged for upload, and where missing dependencies become a generic failure. Done means reducing the upload for a selected module or documenting its unchanged size, and reporting the missing dependency with a useful remedy.

由索引模型根据 Issue 内容生成。

描述

Two quality-of-life improvements for partial deployment via cf deploy -m:

A. Full .mtar uploaded even when deploying a single module

When using -m to deploy one module, the entire .mtar archive is uploaded to the controller. For large MTAs (hundreds of MB with multiple UI, service, and db modules), this adds significant upload time even though only one small module needs processing.

Expected behavior: Either support uploading only the selected module's content (reducing upload time proportionally), or clearly document that upload size is unaffected by -m so developers have correct expectations.
Actual behavior: Full archive is uploaded regardless of -m selection. Deployment time savings from -m are partially negated by the upload step.
B. Dependency errors don't indicate what's missing or how to fix it

When a partial deploy fails because the selected module depends on a resource or module not included in the -m/-r selection and not yet deployed in the space, the error message does not name the missing dependency or suggest the fix.

Expected behavior: Actionable error message, for example:
Module "db-deployer" requires resource "hdi-container" which is not
included in this partial deployment and does not exist in the space.
Add "-r hdi-container" to include it, or deploy it separately first.

Actual behavior: Generic deployment failure message. Developer must manually cross-reference mta.yaml dependencies to figure out what's missing.
Your environment
MultiApps Controller version — SAP BTP managed (latest)
MultiApps CF CLI Plugin version — latest
which CF vendor is used — SAP BTP Cloud Foundry
which backing services are used — hana / hdi-shared (HDI container)
Steps to reproduce
For A (upload overhead):

Build a large MTA (e.g. 200MB+ with multiple UI modules)

mbt build

Deploy only the db module — observe that the full 200MB archive is uploaded

cf deploy myapp.mtar -m db-deployer -r hdi-container

Upload step takes the same time as a full deploy

For B (unclear error):

Attempt partial deploy of db module WITHOUT including the HDI resource

in a fresh space where the HDI container doesn't exist yet

cf deploy myapp.mtar -m db-deployer

Error message does not indicate that "-r hdi-container" is needed

Additional information
SAP's own partial deployment sample warns that "all descriptor validations and dependency checks still run" but doesn't describe the error experience — SAP-samples/cf-mta-examples/partial-build-deploy
The primary use case is iterative HANA Cloud development: a developer changes a single HDI artifact and wants to redeploy only the hdb module without uploading/processing the full MTA.

主要语言
Java
星标
65
派生
41
平均合并
1 天 12 分钟
30 天内合并 PR
7

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cloudfoundry/multiapps-controller 的其他 Issue

查看 cloudfoundry/multiapps-controller 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。