amoravek/Vendor manifests consumer
Extracts and processes vendor manifests
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Jun 9, 2022
- License
- None
Pinned Snippet
uses: amoravek/test-action@c8b3763341a5b330b36c8af46ffe41c28520f238 # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| repository | Repository containing vendor manifest(s) | yes | — |
| ref | Repository ref (branch, tag, commit) | no | — |
| ssh-key | SSH private key (deploy key) for accessing the vendor repository | no | — |
| artifactory-base-url | Target Artifactory repository URL | yes | — |
| artifactory-user | Artifactory user | no | — |
| artifactory-password | Artifactory user password | no | — |
| artifactory-repo | Artifactory target repository | yes | — |
| vendor-metadata-file | Vendor metadata file | yes | — |
| download-user | Username authenticated against the system the files are downloaded from | no | — |
| download-password | Password for that user | no | — |
| identity-file-b64 | Base64-encoded SSH identity file (valid for SCP/SFTP transfers) | no | — |
Outputs
no outputs