Hey there 👋
We have numerous exciting updates in store for you! Let's dive in!
Reminder: Cloud Foundation Community event
We have another Cloud Foundation Community event lined up for June 28th, 9-10.30. You can RSVP for the event by clicking here https://www.meshcloud.io/de/unternehmen/events/cloud-foundation-community-event/. Our highlight: Reiner Bünger from EnBW will be talking about FinOps.
🆕 New name: meshWorkspace
We are excited to inform you that, based on your feedback we will rename meshCustomer to meshWorkspace. This name alteration is aimed at offering a more inclusive and comprehensive representation of the meshStack capabilities. The term "workspace" will help newcomers better understand the meshModel and ensure inclusivity for different hierarchies and structures in various organizations. Over the course of the next 4 weeks, we will update all user-facing assets, including the meshStack UI, documentation, and new API endpoints. However, we will continue to support existing API endpoints for a duration of 1 year to ensure a seamless experience for you.
🟦 Building Blocks Updates
The development of the new Building Blocks feature is continuing at a high pace and there is a lot to share:
Dependencies
Dependencies between Building Blocks can now be defined in meshStack.
Operators can explicitly define that a Building Block depends on another Building Block. They can also define which outputs of the parent Building Block shall be mapped to which inputs of the dependent Building Block.
This enables the implementation of interdependent use cases. For example, a virtual machine Block that depends on a Network Block: the Network Block needs to exist first and provide the network ID to the VM service, so the VM gets connected to the expected network.
Application Teams will only be able to add a Building Block that depends on another Building Block to their meshTenant if the parent Building Block already exists on their Tenant. They can pick exactly which building block should be used (in the case of the example above if you have two network blocks)
Customer users are able to see the dependencies of the building blocks that they have in their tenant control plane.
Delete Building Blocks in Admin Area
Do you want to delete a building block as an operator? This is now possible directly in the Admin Area. In the Building Block section of a Tenant, you will now be able to delete the Building block.
Edit Inputs & Outputs
It is now possible to edit the inputs and outputs of existing building block definitions. As of now, existing building block instances will continue with the old inputs and outputs and if a user wants the new set of inputs and outputs, a new building block instance will have to be created.
We will introduce a proper versioning concept in the future, to bring a better user experience.
Other Delightful Building Block Improvements
- In the Building Blocks tab of the tenant control plane within the admin area, you can now see remarks that might exist for the most recent execution of the selected Building Block. This helps with debugging in cases where no -or only very limited- information is provided via the standard log output. This can happen for example when a user enters the wrong SSH Key for the linked Git repository.
- You can now select a specific path for a Git repository linked to your building block. If your building block code is in a directory, this can now be specified.
- You can now see how many building blocks exist of a certain definition. This should help you get an idea of how popular the building block is. When you are about to delete a building block you will also see this number so you know how large the impact of deletion might be.
- You can now edit the implementation information of an existing building block definition, such as the Git repository URL.
🔑 Password Rotation for API Users
Enjoy enhanced security with new password rotation functionality for API users! There are no restrictions on how many times you can rotate or create passwords, so you have the freedom to repeat this process whenever you like to assure secure usage of the API user.
