Partial deployment (-m): reduce upload overhead and improve dependency error messages
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Java
- Estrellas
- 65
- Forks
- 41
- Merge medio
- 1 d 12 min
- PR fusionados (30 d)
- 7
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de cloudfoundry/multiapps-controller
-
Dificultad 4/5 3-5 días Aptitud para principiantes 53/100
cloudfoundry/multiapps-controller#1945 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
cloudfoundry/multiapps-controller#1943 ·
Los mantenedores suelen responder en 1 día
-
[FEATURE REQUEST] Add additional authentication methods for async file upload from secured remoteAbiertoenhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
cloudfoundry/multiapps-controller#1594 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
cloudfoundry/multiapps-controller#1409 ·
Los mantenedores suelen responder en 1 día
-
support for multiple processesAbiertoenhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
cloudfoundry/multiapps-controller#1365 ·
Los mantenedores suelen responder en 1 día
Todos los issues de cloudfoundry/multiapps-controller
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
apache/skywalking#14239 ·
Los mantenedores suelen responder en 1 día
-
account bug exercise lecture modeling programming
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Posiblemente ocupada @dbusche la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
h2database/h2database#4580 ·
Los mantenedores suelen responder en 1 día
-
vips-drift
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Stirling-Tools/JPDFium#300 ·
Los mantenedores suelen responder en 1 día
-
hermes-queue
Dificultad 1/5 1-3 horas Aptitud para principiantes 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Los mantenedores suelen responder en 1 día