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

オープン
#1,944 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR(30日)
7

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

cloudfoundry/multiapps-controller のほかの issue

cloudfoundry/multiapps-controller の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。