Support data uploader action for next/own clouds (OCS)

[eblondel]

A new action will be configured to support data upload (target with uploadSource data property) into Cloud supported by OCS standard (ie NextCloud, OwnCloud). The remote path can be set using the workspace OCS software property, or using a workspace data property configured for ocs: workspace:someworkspace@ocs

The action will be further fine-tuned depending on needs.

Development sponsored by IRD @juldebar @kikislater

[eblondel]

@kikislater this is now supported in geoflow. This is a "starter" to upload the file specified as uploadSource, but we can enrich further the action to upload all resources available job entity directory.

The action dynamically enrichs the entity pivot metadata model with a relation containing a public read-only link generated by OCS API on top of the resource that is uploaded. This means that plugging this action before an action to generate ISO 19115, the ISO 19115 metadata will inherit from the OCS data file link, and it will be added as Online Resource.

[kikislater]

It works for uploading on Nextcloud with or without workspace. Workspace term is confusing in Nextcloud as it refers to a third party extension. And what happen if we have a lot of configuration to data column, it could be confusing for users dealing with workspace in geoserver. So I suggest to change the name workspace

I think there a mistake in json as "type": is "input" whereas it's an upload function. So "type": "output" works

[eblondel]

i fixed the config example. For the data property, we can use a different one, no issue with that. Do you have a suggestion?

[eblondel]

cloudspace? :-)

[kikislater]

cloud_path seems to be more accurate

[eblondel]

@kikislater here it is, I changed workspace to cloud_path