Feature Requests

As a Platform Engineer I want safety mechanisms regarding the dependencies between Building Block during the upgrade of buidling block definitions. If a Building Block is upgrade to a new released version other building blocks with a dependency might be re-run with unexpected results. Therefore a warning before upgradeing Building Blocks should be displayed with information about: which building block definitions has a dependency on the current BB definition information about the building block instance which has a dependency on the current building block instance

The endpoint List meshProjectGroupBindings ( https://docs.meshcloud.io/api/index.html#_list_meshprojectgroupbindings ) currently allows retrieval of bindings only for a specific workspace and its projects. However, it is also necessary to support retrieving this data across all workspaces and projects, to enable broader visibility and integration.

The endpoint for retrieving workspace user groups ( https://docs.meshcloud.io/api/index.html#mesh_workspaceusergroup ) is currently available only to API users. It would be beneficial to extend support for API keys as well, enabling secure and more flexible access.

Actually building blocks can be checked out from Azure Devops Git repositories with SSH Keys. Unfortunately, SSH keys are not easy to manage: need of an Entra ID user generate secret/public key pair key pair will expire credentials (ssh keys and user credentials) must be rotated via organization policy once a year process is not fully automated A far better way is to authenticate to Azure Devops Git repo via an Entra ID Service principal. Especially because you can authenticate via Identity Workload Federation. See following article how to use git commands with Azure Devops Service principals. https://stackoverflow.com/questions/76465031/azure-devops-pipeline-git-clone-with-service-principal/76519055#76519055 https://stackoverflow.com/questions/67639199/is-it-possible-to-use-service-principal-to-access-git-repository-on-azure/76464678#76464678

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 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.

As a service owner I want to have a nice UX and enforce a manageable overview for my customers. At the moment the Building Block instance name is: at the very bottom of the form -> should be the first field cannot be used as an actual input -> therefore I require my users to input a name for the service instance twice (once as a input and once as a instance name for meshStack only) I cannot update the description of the Building Block Instance name Please expose the Instance Name as potential input for the actual building block provisioning

I have implemented group replication via building blocks. I want my Azure Subscriptions to skip group replication to Entra, because otherwise the Subscription replication and building blocks fight over the same groups.

At the moment I have a building block as part of my landing zone. My application teams are confused to see this Building Block as it is rather an integral part of the Tenant / Landing Zone. It would be great if meshStack would not show this Building Block at all. And if the Building Block has input, to let it show up as "Landing Zone Input"

As a Platform Engineer I want to provide application teams the possibility to trigger Azure DevOps Workflows in self-service.