yc-actions/YC GitHub Runner

GitHub Action to deploy container to Yandex Cloud COI VM

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
modeSpecify here which mode you want to use: - 'start' - to start a new runner; - 'stop' - to stop the previously created runner.yes
github-tokenGitHub Personal Access Token with the 'repo' scope assigned.yes
yc-sa-json-credentialsJSON 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-jsonno
yc-iam-tokenIAM 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-tokenno
yc-sa-idService 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-identityno
folder-idFolder IDyes
labelName of the unique label assigned to the runner. The label is used to remove the runner from GitHub when the runner is not needed anymore. This input is required if you use the 'stop' mode.no
runner-home-dirDirectory that contains actions-runner software and scripts. E.g. /home/runner/actions-runner.no
instance-idId of the created instance. This input is required if you use the 'stop' mode.'no
image-idId of the image that will be used to create boot disk of the VM. This input is required if you use the \u201Cstart\u201D mode.no
service-account-idId of service account that will be attached to VM.no
coresNumber of Coresno2
memoryMemory. Format: `\\d(Mb|Gb)`. E.g. 1Gbno1GB
core-fractionCore fractionno100
disk-typeDisk type. Values: network-ssd, network-hdd, etc. More info https://cloud.yandex.com/en-ru/docs/managed-clickhouse/concepts/storagenonetwork-ssd
disk-sizeDisk size. Format: `\\d(Mb|Gb)`. E.g. 30Gbno30GB
image2-idId of the image that will be used to create a second disk on the VM.no
disk2-typeSecond disk type. Values: network-ssd, network-hdd, etc. More info https://cloud.yandex.com/en-ru/docs/managed-clickhouse/concepts/storagenonetwork-ssd
disk2-sizeSecond disk size. Format: `\\d(Mb|Gb)`. E.g. 30Gbno
zone-idZone IDnoru-central1-a
subnet-idThe subnet ID where the VM will be createdyes
public-ipPublic IP addressnotrue
platform-idCompute platform Idnostandard-v3
runner-versionVersion of the actions-runner softwareno2.320.0
ttlTime to live in ISO 8601 Duration format. E.g. PT1Hno
disable-updateDisable updatenofalse
userUser name to login with via sshno
ssh-public-keyPublic SSH key to login withno
namedescription
labelName of the unique label assigned to the runner. The label is used in two cases: - to use as the input of 'runs-on' property for the following jobs; - to remove the runner from GitHub when it is not needed anymore.
instance-idYC Instance Id of the created runner. The id is used to terminate the instance when the runner is not needed anymore.