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
{{ message }}
This repository was archived by the owner on Dec 29, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: blog/2025-04-30-Release-0.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ This release includes the following issues:
13
13
* Broken Open Source Information in Panel
14
14
* Fix Multirole Mapping for GCP Landing Zones
15
15
* Communications can now target Tenants and BBDs
16
-
* Improved Error Handling for Github Building Block Runner
16
+
* Improved Error Handling for GitHub Building Block Runner
17
17
* Introduction of Communication Center Light
18
18
<!--truncate-->
19
19
@@ -73,11 +73,11 @@ Communication definitions are no longer limited to targeting workspaces. They ca
73
73
#### How to use
74
74
When creating a communication definition, use the filter criteria or API to specify target building block definitions or tenants, either by UUID or by tag. The system will resolve and create one communication per resolved object. workspace ownership is still inferred indirectly via the selected object.
75
75
76
-
### Improved Error Handling for Github Building Block Runner
76
+
### Improved Error Handling for GitHub Building Block Runner
77
77
**Audience:** User<br>
78
78
79
79
#### Description
80
-
If there is a problem while communicating with Github the error handling
80
+
If there is a problem while communicating with GitHub the error handling
81
81
was improved. This results in better error signaling on the affected building
Copy file name to clipboardExpand all lines: docs/meshstack.aks-developer-platform-quickstart-guide.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ Follow the following steps to create a GitHub App that will be used to manage th
60
60
61
61
To make things easy, we will use the [meshStack Hub](https://hub.meshcloud.io) to create the new building block definition.
62
62
63
-
1. Open the Github Repository Creation Definition in the meshStack hub [here](https://hub.meshcloud.io/definitions/github-repository).
63
+
1. Open the GitHub Repository Creation Definition in the meshStack hub [here](https://hub.meshcloud.io/definitions/github-repository).
64
64
2. Click on “Add to meshStack” and enter your meshStack URL (if not given already).
65
65
3. Continue the flow in meshStack.
66
66
1. Right away you will be asked for a “Type”. Pick “Workspace Building Block” here.
@@ -88,11 +88,11 @@ Make sure you save the `config_tf` output and save it as a file called `config.t
88
88
89
89
We will again use the [meshStack Hub](https://hub.meshcloud.io) to create the new building block definition.
90
90
91
-
1. Open the Github Actions Integration with AKS definition in the meshStack hub [here](https://hub.meshcloud.io/definitions/aks-github-connector).
91
+
1. Open the GitHub Actions Integration with AKS definition in the meshStack hub [here](https://hub.meshcloud.io/definitions/aks-github-connector).
92
92
2. Click on “Add to meshStack” and enter your meshStack URL (if not given already).
93
93
3. Continue the flow in meshStack.
94
94
1. Right away you will be asked for a “Type”. Pick “Tenant Building Block” here and select “AKS” as the supported platform.
95
-
2. Continue until you reach the “Dependencies” page. On this page, select the “Github Repository Creation” building block definition that you created before.
95
+
2. Continue until you reach the “Dependencies” page. On this page, select the “GitHub Repository Creation” building block definition that you created before.
96
96
3. Continue until you reach the “Inputs” page. On this page you will be forced to fill in the following:
97
97
1.`namespace` - This refers to the AKS namespace. Open this up and set the “Source” to “Platform Tenant ID”.
98
98
2.`github_repo` - This refers to the GitHub repository to connect to. Open this up and set the “Source” to “Parent Building Block Output” and set the corresponding output to “repo_name”.
Copy file name to clipboardExpand all lines: docs/meshstack.building-pipeline-integration.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,11 @@ Please find below the steps that are required to trigger an external automation
14
14
15
15
### 1. Preparation
16
16
17
-
At the moment we don't provide a native integration into any CI/CD tooling but we offer a neat way to trigger external systems via Building Blocks. In order to trigger a pipeline you may use the Terraform Building Block template below as a place to start. The module below can be used to trigger Github actions, we call this module "Trigger Module".
17
+
At the moment we don't provide a native integration into any CI/CD tooling but we offer a neat way to trigger external systems via Building Blocks. In order to trigger a pipeline you may use the Terraform Building Block template below as a place to start. The module below can be used to trigger GitHub actions, we call this module "Trigger Module".
18
18
19
19
The strucutre of the module is as follows:
20
20
21
-
-[**main.tf**](assets/terraform_examples/pipeline_main.tf): Calls webhooks that are used to trigger Github actions via `terraform apply` and `terraform destroy`
21
+
-[**main.tf**](assets/terraform_examples/pipeline_main.tf): Calls webhooks that are used to trigger GitHub actions via `terraform apply` and `terraform destroy`
22
22
-[**variables.tf**](assets/terraform_examples/pipeline_var.tf): Variables necessary for the integration with GitHub
23
23
24
24
Host your version of the module in a repository of your choice.
0 commit comments