prefapp/Make state repos' dispatches

Dispatch image changes on multiple state repos

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
dispatches_filePath to the config file in the repository. It will be downloaded dynamically from the GITHUB_SHA of the trigger eventyes.github/make_dispatches.yaml
apps_folderLocal path to the apps folder of the .firestartr configurationyes.firestartr/apps
platform_folderLocal path to the cluster folder of the .firestartr configurationyes.firestartr/clusters
registries_folderLocal path to the registries folder of the .firestartr configurationyes.firestartr/docker_registries
tokenGitHub token of a GitHub app or user with `contents:write` permissions over the state repository. It's **mandatory** to pass a PAT token of an user or GitHub app with the needed permission. yes
read_tokenGitHub token with permissions for operations in the repository where the action is used (defaults to GITHUB_TOKEN) yes${{ github.token }}
image_typeImage types to filter in the dispatches file (releases, snapshots, *). Default to all (*) no*
flavorsFilter dispatches by flavor, can be multiple values separated by commas.nodefault
filter_by_envDispatch only to dispatches whose environment is included in this filter, if specified. Can be a comma separated list of environments or * (all) yes*
filter_by_tenantDispatch only to dispatches whose tenant is included in this filter, if specified. Can be a comma separated list of tenants or * (all) yes*
filter_by_platformDispatch only to dispatches whose platform is included in this filter, if specified. Can be a comma separated list of clusters or * (all) yes*
overwrite_versionDispatch using this version instead of the one defined in the dispatches file (can be a short-sha or a release tag) no""
overwrite_tenantDispatch using this tenant instead of using the one defined in the dispatches file, related to the flavor to deploy. no""
overwrite_envDispatch using this environment instead of using the one defined in the dispatches file, related to the flavor to deploy. no""
default_releases_registryDefault registry to use when dispatching releasesno
default_snapshots_registryDefault registry to use when dispatching snapshotsno
reviewersList of reviewers' login username, separated by commas, to include in the state repo pull request. no""
build_summaryBuild summary of the last call to build_images.yamlno""
check_run_nameName of the check run where the build summary will be uploadedno""

no outputs