Feature Requests

at first, I wasn’t a big fan of this, but with more custom platforms emerging, it’s a must-have. It allows us to roll out some of them (Tencent, IONOS, StackIT) more easily across different CSPs without being tied to a specific vendor.

As a meshStack admin, I want to add and update the help link for my application teams directly in the admin area under settings, so I can make changes myself without contacting meshcloud support.

We would like to request the feature to retrieve information about all created building blocks in the workspace as part of a building block definition. A possible and probably elegant way to do that would be to extend the "context metadata" input variable types with a type for "Workspace Building Blocks". Comparable to other "context metadata" input types, this input would hold a list of building blocks that are currently booked under the workspace (probably including the one that contains the input itself in case that building block was created), and would dynamically trigger updates on the building block with this input as soon as new building blocks are created/updated/removed. The list of building block can then be iterated, filtered and processed inside the Terraform code. Having this kind of input would allow to handle relations between building blocks, that are currently very limited (one building block can only depend on one other), in the most flexible way. One building block might want to get information about other building blocks in order to implement certain permission structures or other "orthogonal" concerns.

At the moment only a few currencies are supported by default in the automated currency exchange configuration. It would be great to extend the supported currencies to CHF

As the platform owner, it is essential to provide the customer with a comprehensive end-to-end sandbox experience, enabling them to create and delete meshObjects in an entirely automated fashion. The desired capabilities have various functionalities, including but not limited to: Creation and Deletion (marking for deletion) of sandbox tenants, projects, or even customers. Onboarding and offboarding of teams. Acquisition of payment method information. By providing these capabilities, we empower our teams and clients to develop customized automation tasks, thereby enhancing the overall user experience.

Entra allows to scope group/user management to administrative units. Supporting this in meshStack will allow finer grained access control. More information on Administrative Units: https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/administrative-units

As a Workspace Owner/Manager I want to be notified (e.g. via mail) if a collegue has created/deleted tenants to ensure, that (urgent) measures can be taken if the tenant has accidently been deleted (created).

It's possible to dynamically configure a backend for Terraform using the -backend-config parameter ( docs ). It would be great if this option was available for Building Blocks. Using a TF_CLI_... environment variable does not work because the environment is sanitized before executing Terraform.

It would be great if the frontend would show a browser dialogue message warning that you're about to leave the page whenever you're inside of the form to create a new building block definition. That could be a message like "Are you sure you want to leave the page?" Since building block definitions can take a significant amount of time to create (considering the definition of inputs/outputs) it would be a shame to lose all progress, e.g. just because you accidently clicked a link in the sidebar.

As a platform engineer I'd like to offer Building Blocks on a Workspace level as they do not relate directly to any particular project, but they are rather a global service for the entire workspace.