You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This GitHub Action registers building block sources and steps with meshStack. It integrates with the meshStack API to set up the structure of a building block run with the specified steps.
3
+
This GitHub Action registers building block sources and steps with meshStack. It integrates with the meshStack API to set up the structure of a building block run with the specified steps. This allows platform teams
4
+
to provide additional feedback about building block execution to application teams.
4
5
5
6
## Overview
6
7
7
-
The meshStack building block pipeline allows you to automate and manage complex workflows by defining a series of steps that need to be executed. Each building block run represents an instance of such a workflow. This GitHub Action helps you register the source of the run and define its steps.
8
+
A meshStack building block run allows you to automate and manage complex workflows by defining a series of steps that need to be executed. This GitHub Action helps you register the source of the run and define its steps.
8
9
9
-
In order to return updates for a run to meshStack, you first need to register one or multiple steps and their resources of your run execution. It is up to you how many or how you organize your steps. You can, however, also just send step results back and the registration takes place on the fly. But in order to have a consistent display and ordering of steps, it is highly advised to pre-register steps and sources.
10
+
It is up to you how many or how you organize your steps. You can, however, also just send step results back and the registration takes place on the fly. But in order to have a consistent display and ordering of steps, it is highly advised to pre-register all steps that you plan to execute.
10
11
11
12
## Related Actions
12
13
@@ -30,38 +31,77 @@ For more information, refer to the [meshStack documentation on building block in
30
31
31
32
## Inputs
32
33
33
-
-`client_id` (required): The client ID for the API.
34
-
-`key_secret` (required): The key secret for the API.
35
-
-`steps` (required): The steps to register.
34
+
-`steps` (required): JSON array of steps to register. Each step should have an `id` and `displayName`.
36
35
37
-
###Outputs
36
+
## Outputs
38
37
39
38
-`token_file`: Path to the file containing the authentication token
39
+
- Dynamic outputs based on building block inputs (e.g., custom parameters defined in your building block)
40
+
41
+
## Required GitHub Context Parameters
42
+
43
+
This action requires the meshStack workflow trigger parameters to be present in the GitHub event payload:
44
+
45
+
-`buildingBlockRunUrl` (required): URL to fetch the building block run object from the meshStack API
46
+
-`buildingBlockRun` (optional, legacy): Base64-encoded building block run object (alternative to `buildingBlockRunUrl`)
47
+
48
+
These parameters are automatically provided by meshStack when it triggers your workflow via `workflow_dispatch`.
0 commit comments