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

Ouverte
#1,944 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
java
Domaine
backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Java
Étoiles
65
Forks
41
Merge moyen
1 j 12 min
PR mergées (30 j)
7

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de cloudfoundry/multiapps-controller

Toutes les issues de cloudfoundry/multiapps-controller

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.