scality/Artifacts Setup
Set outputs to work with Artifacts Actions
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| url | The url of Artifacts | yes | — |
| user | The user to authenticate with Artifacts. Usually setup as a secret in the organization, ask your admin for the key name. | yes | — |
| password | The password to authenticate the operation with Artifacts. | yes | — |
| method | What kind of interaction you will perform with Artifacts. With the choice of: setup, upload, promote, prolong. | yes | — |
| name | The name of the artifacts build you will use. Only used with prolong and promote method | no | default |
| tag | The git tag name of the artifacts you are going to promote. To be used with `promote` method. | no | default |
| source | File or directory to upload. To be used with the upload method. | no | . |
| workflow-name | Name of the workflow file you want to have the Artifacts name. | no | default |
| args | List of key value pairs to set when indexing metadata on Artifacts Example: args: | key=value foo=bar | no | — |
| token | The GitHub Personal Access Token (PAT) | no | ${{ github.token }} |
Outputs
| name | description |
|---|---|
| name | The name of the artifacts for a specific workflow. This name will be unique for the whole workflow and can be used by further steps to locate the artifacts inside a job. |
| link | The full url in which artifacts will be stored. |
| redirect-link | The full url that will redirect clients to a pre-signed S3 url providing data through the S3 bucket instead of the Artifacts service. |