Feature Requests

As an Application Developer, I want to manage my service instances via code to have all my infrastructure in Git and version controlled.

Description: When editing landing zone properties, users are required to input specific quota values. These values must fall within a predefined range (min/max) set at the platform level. Currently, these platform-level limits are not visible within the UI, making it difficult for users to input valid values confidently and efficiently. Request: Add a visual reference in the landing zone properties editing UI to display the current platform-level quota limits (min/max values). This will ensure users can easily provide accurate inputs without having to reference external documentation or guess the limits. Benefit: Improves user experience by reducing trial and error. Reduces validation errors. Ensures quicker and more accurate configuration of landing zones.

I am a developer in an application team. The service catalog offered by our colleagues from the cloud foundation team includes many services offered via service brokers. We would like to do project and service management using terraform. Besides project and tenant creation, we want to order services offered via service brokers.

For troubleshooting purposes I need to be able to figure out which building block run was running when and which output it produced. Right now, building block runs are deleted once the building block is deleted. Recently I forgot to add terraform state to my building block and all deletions went through succesfully, however the instances stayed there. Took me a long time to figure out what I did wrong. It would have helped immensely if I could have seen the deletion logs.

I have a Terraform resource in SAP BTP ( https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_entitlement ) that has an optional amount field. I'd like to ask this to my users but also let them skip it if they want to.

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.

I have a pipeline that I built in GitLab. I'd rather have meshStack directly trigger this API instead of using meshStack's Terraform implementation to add a file into a repository.

As an engineer I want to manage my Building Block Definition via API (or ideally even via Terraform) so I can manage the Terraform code and the definition information as one asset, and I won't have to go into the UI anymore to make changes.

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.

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?"