Allow to set remote files field at creation

CHANGELOG.md

@@ -3,7 +3,7 @@
 ## 1.2.4 (unreleased)
 
 
-- Nothing changed yet.
+- Allow to set remote files field at creation
 
 
 ## 1.2.3 (2024-01-16)

docs/03-kb.md

@@ -69,6 +69,7 @@ You can also set the contents of the resource, as fields:
 - Text fields in `texts`
 - Link fields in `links`
 - Conversation fields in `conversations`
+- File fields in `files` if they are provided as an URI (passing a binary file is not supported, you need to use the [`upload` command](./04-upload.md)).
 
 Note: you cannot set File fields when creating a resource, you need to use the [`upload` command](./04-upload.md).
 
@@ -80,6 +81,7 @@ Examples:
   nuclia kb resource create --slug=my-resource
   nuclia kb resource create --origin='{"collaborators":["THE_AUTHOR"]}' --usermetadata='{"classifications": [{"labelset": "SOME_CATEGORY", "label": "SOME_VALUE"}]}'
   nuclia kb resource create --texts='{"chapter-1": {"body": "here is a test", "format": "PLAIN"}'
+  nuclia kb resource create --files='{"chapter-1": {"file": {"uri": "https://somewhere.com/file.pdf", "filename": "file.pdf", "contenttype": "application/pdf"}}}'
   ```
 
   IMPORTANT: when using the CLI on Windows, you need to escape the double quotes in the JSON strings, like:

nuclia/sdk/resource.py

@@ -15,6 +15,7 @@
     "conversations",
     "links",
     "texts",
+    "files",
     "usermetadata",
     "fieldmetadata",
     "title",