Expected behavior:

• When I submit a non-file form part that has not one of the reserved keywords as name (see https://docs.camunda.org/manual/7.10/reference/rest/deployment/post-deployment/#request-body for those), then a status 400 is returned with an error message indicating that the form part is not recognized

Current behavior:

• NullPointerException, because we always treat such a form part as a file form part and add a deployment resource with name null

Context:

NOTE: It was thought to be a tenant issue, but it is only the bad speling of parameter tenant-id that cause the crash.

can be reproduced with latest docker images:
docker pull camunda/camunda-bpm-platform:latest
docker run -d --name camunda -p 8080:8080 camunda/camunda-bpm-platform:latest

assuming some bpmn file available, specifying -F "tenand-id=tenant1"
make call crash, while not specifying it works.

curl -w \n -H Accept: application/json -F "deployment-name=reporting" -F "enable-duplicate-filtering=true" -F "deploy-changed-only=true" -F "tenan*d*-id=tenant1" -F "workflow.bpmn=@./reporting/src/main/resources/bpmn/workflow.bpmn" http://localhost:8080/engine-rest/deployment/create

First org.camunda stack: org.camunda.bpm.engine.rest.filter.CacheControlFilter.doFilter(CacheControlFilter.java:41)
org.camunda.bpm.engine.rest.filter.EmptyBodyFilter.doFilter(EmptyBodyFilter.java:97)
</pre><p><b>Root Cause</b></p><pre>java.lang.NullPointerException
org.camunda.bpm.engine.impl.AbstractDefinitionDeployer.isResourceHandled(AbstractDefinitionDeployer.java:81)
org.camunda.bpm.engine.impl.AbstractDefinitionDeployer.parseDefinitionResources(AbstractDefinitionDeployer.java:70)
org.camunda.bpm.engine.impl.AbstractDefinitionDeployer.deploy(AbstractDefinitionDeployer.java:61)