ram-repo/DAAP Build & Publish

Validates version bumps, builds package zips, and publishes them to Artifactory. Accepts a multiline data-product-paths input to process one or more products in a single call.

Trust Signals

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

Inputs

name	description	required	default
data-product-paths	One entry per line. If a path has manifest.yaml at its root it is used directly (explicit / co-location mode). If it does not, every immediate subdirectory is scanned (mono-repo mode); subdirs without manifest.yaml are skipped silently. Both plain and YAML list format (leading "- ") are accepted.	yes	—
data-assets-path	Root path for all data assets. Assets are resolved at <path>/<package_id>/<asset_id>/. Typically "data-assets" at the repo root but any relative path is accepted.	yes	—
artifactory-username	Artifactory username	yes	—
artifactory-password	Artifactory password. Also used for Docker registry login to pull the DAAP CLI image.	yes	—
artifactory-package-url	Full URL to the target Artifactory package repository (production or snapshot). The consumer workflow is responsible for routing to the correct URL based on trigger type.	yes	—
base-sha	Base commit SHA for change detection and version bump diff. On PR events: github.event.pull_request.base.sha On branch pushes: HEAD^1 (computed in consumer workflow) On tag push: leave empty — change detection is skipped and all products are published unconditionally. On workflow_dispatch with explicit products: leave empty.	no	""
head-sha	Head commit SHA for change detection and version bump diff. On PR events: github.sha On branch pushes: HEAD (computed in consumer workflow) Leave empty when base-sha is empty.	no	""
skip-version-check	When true, skips the manifest.yaml version bump check. Set to true for all non-PR triggers (post-merge, branch push, tag push, dispatch). The version was already validated on the open PR.	no	false
allow-overwrite	When true, passes --force to "daap package publish", allowing overwrite of an existing artifact at the same version in Artifactory. Independent of artifactory-package-url — both snapshot and production combinations are valid (e.g. allow-overwrite=true + production URL on tag push).	no	false
docker-registry	Docker registry hosting the DAAP CLI image	no	gart.software.power-v.com

Outputs

name	description
published-packages	Newline-separated list of all package_id values successfully published. Pass directly to daap-deploy's packages input via ${{ needs.publish.outputs.published-packages }}.
package-ids	Newline-separated list of package_id values (one per resolved path, same order as input).
versions	Newline-separated list of version values (one per resolved path, same order as package-ids).