Feature Requests

When I have a terraform module with a name like "workspace_identifier" meshStack right now detects this as a simple string user input. It would be a nice convenience if meshStack automatically recognized a few common patterns and set the right types instead workspace_identifier => Source: Workspace Identifier project_identifier => Source: Project Identifier account_id, subscription_id, project_id => Source: Platform Tenant Id

I would like to have the ability to perform "dry-run" executions on Terraform building blocks. This would allow me to preview the output of terraform plan before executing an actual terraform apply . This feature would be especially useful in scenarios such as: Upgrading building blocks: Validate changes introduced by version updates before applying them. Testing inputs: Confirm that inputs to a module behave as expected. Essentially getting insights on potential changes without affecting infrastructure.

As a platform engineer I want to get an ephemeral (short-lived, limited purpose) API key for meshStack in my building block run. This would enable me to interact with meshStack as part of a building block run (e.g. provision a new building block in the background) without needing almighty admin permissions. The UI should show in the marketplace when a building block uses this so it is transparent to users what side effect certain building blocks might have. It could show for examlpe "This building block has the permission to provision other building blocks in your workspace.". My use case is that I want to provide an "extension" of another building block. Rather than defining a dependency and having the user book both, I want to automatically create a Building Block via Terraform in the background.

I'm working on a new building block and have a few runs failing due to issues with my terraform code. I have to go back from runs to the definition a lot to fix inputs and outputs configuration. When I'm on the run page there's no direct link to help me fix my output configuration. The run list screen on the other hand includes two links to the definition (big button at the top right and the definition name underneath the UUID is also a link).

I want my app teams to be able to read the system messages from Building Blocks. Perhaps there is a simple overlooked validation message where they can see how to fix their problem

I want to be able to validate building block inputs of type "user input" dynamically via API. So when a user inputs something into the field I want to be able to check on the fly if the input is valid. Another option could be that a dropdown list of valid inputs is shown instead. This could for example be a list of valid email addresses in the company. Similar to: https://meshcloud.canny.io/feature-requests/p/billing-information-validation

Currently I can use either Terraform or Github Actions to manage resources encapsulated in a building block. If I want to use any other tool or call an API directly I have to wrap it in terraform or run it in Github. Instead I want to be able to run custom code directly or call any API.

A validation workflow, including the specification of an approver, will be integrated into the marketplace services development. Upon a user's request for a marketplace service, the system will route the request to the designated approver for review. The approver can reject the request and include an optional note. Rejected requests may be revised and resubmitted, or the user can initiate a new request. Provisioning will only occur for requests that have received approval.

As a building block developer I want to be able to retrieve the building block objects that are based on my building block definitions in the service management area. I can already see the info I want in the UI, but I cannot access it via API. The only way to get building block objects via API is to request an API user from an admin that has the "Get any MeshObject" permission. This allows access to much more than needed though and is incompatible with least privilege principles.

I have a database building block that allows users to specify optional high availability (HA) settings. If a user selects the "Enable HA" checkbox, I want additional input fields to be displayed for specifying HA details.