Feature Requests

To make the marketplace better looking we should show all marketplace services in a grid view.

Goal: When retrieving AWS costs, also retrieve the Seller ID (e.g., AWS, AWS Marketplace) for each product. This will enable us to differentiate cost items by seller. The Problem: AWS issues two types of invoices: An invoice per seller (used by our ERP for accounts payable), which lacks detailed billing data. An invoice per account, which provides detailed product-level data but does not contain the Seller ID. The Challenge: Our ERP needs the detailed billing data from the per-account invoice but also requires the Seller ID from the per-seller invoice.

I want to quickly test an OpenTofu building block with meshStack. Setting up a private git repo + ssh key and committing files to git every time is a bit cumbersome and I thought I could just abuse the code input to inject a main.tf file and use an otherwise empty git directory. Unfortunately only the "file" input type supports "provide as file". So for now I have to upload a file to meshStack everytime to make changes. It would be very handy to have an inline editor instead.

When I receive a new communication as a workspace owner, that communication is only shown deeply nested in Compliance > Communications and a hint that new communications exist in the Workspace Overview. As a platform team I'm worried that both are not prominently enough featured so that my applications teams miss out on them.

Centralized log management can greatly enhance end-to-end visibility and the security stance by enabling the extraction of audit logs/events from meshStack for import into an external tool such as a SIEM system.

As a Cloud Foundation Administrator I want to prevent empty workspaces and project to keep the meshStack organized. At the moment neither the workspace nor the project view in the admin area provides information if the cloud account or service registry is actually used (e.g. consumption, number of instances, etc.). Currently I must dig deeper into the individual Usage Reports to get an indicator if a project still has instances or if the cloud accounts are in use. Therefore I would require a quick overview with filters, search and actions to find orphaned, empty or non used project and workspace.

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.

The current process for creating a new service account with a designated role in Azure or GCP involves users submitting a ticket for the operations team to manually provision. This workflow needs to be streamlined and enhanced. Given that meshStack is the optimal solution for managing cloud resources, we should offer this service (via the marketplace?). Users need to be able to: Provision new service accounts in Azure and GCP with designated permissions/roles. Modify permissions for existing service accounts. To facilitate this, the user interface must dynamically retrieve and display the roles and permissions a user is authorized to assign. This requires a live lookup of roles and Service Principal Names (SPNs) from the cloud, a capability that is not supported by static data sources like meshStack building blocks or ServiceNow requests.

Hey, it would be really useful to have a schedule feature that allows re-running building block instances. For example this would allow automatic, recurring rotations of secrets that are deployed by a BB without any additional infrastructure. Or this would make it possible to have BB instances automatically updated to the latest Terraform definition without further user interaction. I could imagine an extra option in the BB definition to allow running BB instances on a schedule by defining a Cron schedule or something like that. This should apply to all existing BB instances. Kind regards Martin

As a FinOps Team I require cost items in meshStack to be reflecting list prices. Therefore we defined a cost collection pipeline which imports the cost and line items as Usage Reports. Additionally the kraken configuration needs to be added with dumm/placeholder variables. At the moment the finalization of these imported Usage Reports are not working as the state collection progress is not updated. The current workaround is that CUS is updated the document in RavenDB manually once a month.