Juan,

That is correct, you do not need to call /v2/resource_match. I am not sure
what you mean by being able to upload the structure(?) but the files being
empty. If you could clarify that would be helpful.

An important aspect to note about the "/v2/apps/:guid/bits" endpoint is
that it expects a multipart PUT to be sent to it. The API docs here[1]
should help. In your case, the resources block would be an empty array
since you are not using resource matching.

- Chris Piraino

[1]:
http://apidocs.cloudfoundry.org/214/apps/uploads_the_bits_for_an_app.html

On Thu, Aug 6, 2015 at 2:31 PM, Juan Antonio Breña Moral <
bren(a)juanantonio.info> wrote:

Hi Arthur,

My initial idea, is the development of a Node.js client to upload
application to CF.
Reading your lines, I understood that It is not necessary to execute the
method: /v2/resource_match , is it correct? So, I only would have to
execute the method:

'/v2/apps/' + app_guid + '/bits'

Today, I was doing some tests and I am able to upload the estructure, but
files are empty. What is the problem with the files? Is it something
related with the method: "/v2/resource_match"?

Many thanks in advance.

Note: I think that exist some hours of delay using this mailing list.
Github is realtime I mean. :)