yc-actions/YC Object Storage Upload

GitHub Action to upload files to Yandex Cloud Object Storage.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
yc-sa-json-credentials	JSON containing authorized key for Service Account. Either this or `yc-iam-token` or `yc-sa-id` should be provided. More info https://cloud.yandex.ru/docs/container-registry/operations/authentication#sa-json	no	—
yc-iam-token	IAM token for Yandex Cloud. Either this or `yc-sa-json-credentials` or `yc-sa-id` should be provided. More info https://yandex.cloud/ru/docs/iam/concepts/authorization/iam-token	no	—
yc-sa-id	Service Account ID. Will be uses to exchange GitHub token to Yandex Cloud token. Either this or `yc-iam-token` or `yc-sa-json-credentials` should be provided. More info https://yandex.cloud/ru/docs/iam/concepts/workload-identity	no	—
bucket	Object Storage bucket name for code	yes	""
prefix	Prefix that will added to all keys.	no	""
root	Path that will considered as root.	yes	—
include	Patterns to include. Multiline	no	*
exclude	Exclude patterns. Multiline	no	""
clear	Clear bucket before upload.	no	false
cache-control	Cache-Control header value. Multiline. Path mapped to value.	no	""
concurrency	Maximum number of files uploaded in parallel. Values below 1 are clamped to 1, values above 256 are clamped to 256.	no	16
skip-unchanged	When true, skip uploading a file if the remote object's ETag matches the local file's MD5. Content-only comparison: a change to cache-control alone will not trigger a re-upload, and multipart objects are always re-uploaded.	no	false
fail-on-error	When true, the action fails if one or more files could not be uploaded (after attempting every file). When false (default) upload errors are only logged, preserving the previous behavior.	no	false

Outputs

no outputs