Partial deployment (-m): reduce upload overhead and improve dependency error messages
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 45/100
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- Java
- Estrelas
- 65
- Forks
- 41
- Merge médio
- 1d 12min
- PRs com merge (30d)
- 7
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de cloudfoundry/multiapps-controller
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 53/100
cloudfoundry/multiapps-controller#1945 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 35/100
cloudfoundry/multiapps-controller#1943 ·
Mantenedores costumam responder em até 1 dia
-
[FEATURE REQUEST] Add additional authentication methods for async file upload from secured remoteAbertaenhancement
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
cloudfoundry/multiapps-controller#1594 · 4 comentários ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 25/100
cloudfoundry/multiapps-controller#1409 ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 42/100
cloudfoundry/multiapps-controller#1365 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de cloudfoundry/multiapps-controller
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
apache/skywalking#14239 ·
Mantenedores costumam responder em até 1 dia
-
account bug exercise lecture modeling programming
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 64/100
Mantenedores costumam responder em até 1 dia
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Talvez já em andamento @dbusche assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
h2database/h2database#4580 ·
Mantenedores costumam responder em até 1 dia
-
vips-drift
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
Stirling-Tools/JPDFium#300 ·
Mantenedores costumam responder em até 1 dia
-
hermes-queue
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Mantenedores costumam responder em até 1 dia