actions-marketplace-validations/Create Mender artifact module-image
Create an mender artifact file
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Mar 9, 2023
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/kevinrohn_create-mender-artifact@6627a62da8f1c5214bf9c6647b56f9cb3e72f83f # no releases — HEAD as of 2026-07-12tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| artifact-name | Name of the artifact | yes | — |
| device-type | Type of device(s) supported by the Artifact. You can specify multiple compatible devices providing this parameter multiple times. | yes | — |
| type | Type of payload. This is the same as the name of the update module. | yes | — |
| artifact-content | Content for the artifact payload, based on the payload type. | yes | — |
| output-path | Full path to output artifact file. | yes | — |
| state-scripts | Full path to the state script(s). You can specify multiple scripts providing this parameter multiple times. | no | — |
| software-name | Name of the key to store the software version: rootfs-image.NAME.version, instead of rootfs-image.PAYLOAD_TYPE.version. | no | — |
| software-version | Value for the software version, defaults to the name of the artifact. | no | — |
Outputs
| name | description |
|---|---|
| path-to-artifact | The path to the generated mender artifact. |