FEATURE REQUEST: File Upload via REST API

[bjv]

I'd like to request a possibilty to upload files to Assets (and maybe other entities) via REST API.

I found #5007 requesting the same issues and was wondering that this still is not possible.
Seems to be a feature of high value and potential.

Alternatively, I could image a feature attaching files via an php artisan snipeit:import but REST API seems more suitable.

Thank you!

[PetriAsi]

@snipe I could have some time to write PR for this, after v6 is out. If I do, how following api path plan look to you?

/hardware/[asset_id]/files (GET -> List uploaded files for asset)
/hardware/[asset_id]/files (POST -> upload new file(s) with optional notes)
/hardware/[asset_id]/files/[file_id] (GET download file)
/hardware/[asset_id]/files/[file_id] (DELETE download file)

I planned to use AssetFilesController as starting point, extend it to support base64 encoded files same way as image upload api does.

[NocturnalNick]

@snipe I could have some time to write PR for this, after v6 is out. If I do, how following api path plan look to you?

/hardware/[asset_id]/files (GET -> List uploaded files for asset)
/hardware/[asset_id]/files (POST -> upload new file(s) with optional notes)
/hardware/[asset_id]/files/[file_id] (GET download file)
/hardware/[asset_id]/files/[file_id] (DELETE download file)

I planned to use AssetFilesController as starting point, extend it to support base64 encoded files same way as image upload api does.

I would love this functionality, and those endpoints are perfect.

Perhaps as a stop-gap solution (that would work well in my use-case at least) when an asset's "image" is replaced (using /hardware/id:PUT) the older image could be relegated to the uploaded files instead of removed?

[snipe]

This was already done, no? https://github.com/snipe/snipe-it/pull/9767

[NocturnalNick]

This was already done, no? #9767

I might be misunderstanding that other thread but it seems to be talking about the single image associated with an asset. I've got that set up ok, but any new upload replaces the old one, and in my case I'm tracking possible degradation/damage over time, so need to have older points of reference if, say, a key was pried off by the previous user (or 3 users back and went unreported)

[PetriAsi]

Yes, currently only image uploads are done. Same code will work for file/attachment uploads, after some tweaks.

[NocturnalNick]

The big thing for me is to keep a history/record of uploads, not just the most recent image. I'm fine if it's the same API/endpoint, I just want the images not to replace one another.

[PetriAsi]

@NocturnalNick does snipe it keep history of images currently when using browser to upload/change images?

[NocturnalNick]

@PetriAsi No. If you upload the image in the "Edit Asset" page it won't keep the old ones. You can upload a file/attachment to the asset and it'll stay there, but there's no API endpoint for that (yet, that's what I'm asking for here)

[bjv]

Hej Guys! @snipe just to make clear I (and probably @NocturnalNick and @PetriAsi ) am asking of uploading attachments to an asset, as shown here:

not just an image to be displayed as the asset's device image

I think this has not been done with #9767
Correct me if I am wrong guys

[NocturnalNick]

That's what I want too, I was just saying that we CAN upload an image currently as the device image, and at least for my purposes it would suffice if those device images were kept as a history. I'd rather have file upload functionality as you are after instead, but if new endpoints aren't as easy as adjusting behaviours of old ones...

[MeisterJoghurt]

i am also interested in the feature described by @bjv the solution @PetriAsi described would be exactly what we need.

[HendrikClijstersMosa]

+1 on the comment made by @MeisterJoghurt .

[ShaunNeighbourSwale]

Was this ever implemented? If so, does it also handle user photos?