Feature Requests

As a platform engineer I want to list building block runs via the API. I have the following use cases in mind: Batch update the status of several Building Blocks in one go (by listing the BBs and getting the list of runs that are pending) Make my automations be able to provide status just by having the BB ID instead of needing to pass it the run ID Detect if a Building Block run was the first run, or if it was re-run by an admin (by fetching the list of runs for that BB) Get statistics of Building Block runs, for example, list all runs that failed / were stuck in progress

While setting up a new Building Block or debugging an existing one I must frequently switch between the definition and instances of this Building Block because the workflow is usually like this: change definition release new version upgrade Building Block to test new version repeat I'd love to have a "go to definition" button when looking at a Building Block and vice versa a "show Building Blocks" button while looking at the definition.

As a platform engineer, I have a list of options the user can select (single select). These options however are quite technical as they need to go into Terraform. I wish I could pick a display name for these values so I can show the user something human-readable and easy to understand while still supporting the technical name under the hood.

As a platform engineer I want my users to select multiple options out of a list of options for a building block input. For example, I might need an array of options as a variable in Terraform

As a meshstack user, I don't want to be aware of the mandatory building blocs in a landing zone in order to order platforms more hazzlefree. Actually, as an end user, the bb name has to be confirmed, althoug I do not know the purpose and the meaning of the building block since it comes automatically with the landing zone.

As a platform engineer I'd like to get the email address of the user triggering a building block run as a input variable. Currently, the building block definition allows me to add the tenant user permissions as an input variable. In my case, I would also need the email address of the user starting the run. This could be achieved as a flag within the user permissions array, e.g. [ { "meshIdentifier": "abc-def-hij", "username": " mail@example.com ", "firstName": "Firstname", "lastName": "Lastname", "email": " mail@example.com ", "euid": " mail@example.com ", "roles": [ "user" ] is_current_user: (true|false) } ] or as a separate input variable, e.g. current_user: " mail@example.com " Thank you, André

I'm developing a new Building Block that triggers a GitHub actions pipeline and try to use the new source/step reporting API. During development, my pipeline sometimes fails due to a coding error in the pipeline. In this case, the building block run gets "stuck" in meshStack. I notice little visual indication that the run is stuck, i.e. the "Prepare run step" is green but nothing more indicates that it's waiting (for my pipeline or any other system) to report status there's no way to cancel the "stuck run", so that I can trigger a new run with a "fixed" version of my pipeline code The only workaround I have found is trying to purge the building block and create a new one. Purging the BB seems not to be immediately effective, and this litters my development environment with test building blocks

I want to use tag values (like the environment the tenant is in) in my building block definitions. Depending on the environment, my building block can be multi-region for prod (higher availability) or single-region for dev (cheaper) in the case of storage.

What I want to do: The azurerm terraform provider allows to manage firewall_application_rule_collection (see https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/firewall_application_rule_collection ) with rules inlined. It does not allow to manage rules outside of this single resource definition. This means managing firewall rules is not doable effectively with meshStack building blocks without the support for complex inputs. In this example, the input needs to be a list of firewall rules.

As an owner of a Building Block Definition it can be a lot of work to roll out an upgrade to all my Building Blocks for very simple things as just updating a single static input. It would be great if meshStack automatically pushes through these kind of upgrades, perhaps after asking me "Your new version has been published, do you want to upgrade all Building Blocks automatically?"