nspcc-dev/Publish to NeoFS

This action allows you to publish files, tests reports, static web pages and etc. to NeoFS

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
NEOFS_WALLETBase64-encoded NEP-6 Neo N3 wallet for NeoFS network access. See the README.md for more informationyes
NEOFS_WALLET_PASSWORDN3 wallet passwordyes
NEOFS_ENDPOINTRPC endpoint for NeoFS node (e.g. grpcs://st1.storage.fs.neo.org:8082 or grpcs://private-node:9090). nogrpcs://st1.storage.fs.neo.org:8082
HTTP_URL_PREFIXFull URL prefix used to build OUTPUT_CONTAINER_URL (e.g. https://rest.fs.neo.org/MYCID/ or https://reports.example.com/). If not set, the container URL will be built as https://rest.fs.neo.org/$STORE_OBJECTS_CID/ and if URL_PREFIX is set, it is appended to https://rest.fs.neo.org/$STORE_OBJECTS_CID/$URL_PREFIX/. no""
STORE_OBJECTS_CIDContainer ID for your datayes
PATH_TO_FILES_DIRPath to the directory with the files to be pushedyes
NEOFS_ATTRIBUTESUser attributes in form of Key1=Value1,Key2=Value2no
URL_PREFIXPrefix added to the FilePath attribute of each uploaded object (e.g. a run ID like "96-1697035975"). When HTTP_URL_PREFIX is not set, also appended to OUTPUT_CONTAINER_URL. no
LIFETIMENumber of epochs for object to stay validno0
REPLACE_OBJECTSReplace existing objects with the same attributes in the containernoTrue
REPLACE_CONTAINER_CONTENTSRemove all the old existing objects in the container after the new objects are uploadednoFalse
namedescription
OUTPUT_CONTAINER_URLContainer URL