|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.41.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-09-17 to 2025-09-24 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Allow Tenant Import Into Custom Platforms Without Mandatory Building Blocks |
| 10 | +* Fixed Building Block Execution Loop Issue |
| 11 | +* Enable Editing Assignment Type for Building Block Outputs in Draft Mode |
| 12 | +* Improved Terraform Variable Detection for Building Block Definitions |
| 13 | +* Refresh Buttons for Building Block Lists |
| 14 | +* Fix AWS Landing Zone Creation via Platform Builder |
| 15 | +* Hide Building Blocks Without User Input From Creation Wizards |
| 16 | +* Workspace Building Block Preselected by Default during Definition Creation |
| 17 | +* Auto-select Current Workspace when Returning from meshStack Hub |
| 18 | +* Fix GitHub Workflow Validation for Building Block Definition Purge Mode |
| 19 | +* Improve Admin UI layout and extend app background |
| 20 | +* Enable SSH Authentication for Terraform Modules in Building Blocks |
| 21 | +* Improved Default View Toggle for Workspace Overview |
| 22 | +* Default Settings for Feature Previews |
| 23 | +* Fixed multiple scrollbars in Admin Area sidebar |
| 24 | +<!--truncate--> |
| 25 | + |
| 26 | +## Ticket Details |
| 27 | +### Allow Tenant Import Into Custom Platforms Without Mandatory Building Blocks |
| 28 | +**Audience:** User<br> |
| 29 | + |
| 30 | +#### Description |
| 31 | +Fixed a regression that prevented importing tenants into custom platforms when the landing zone |
| 32 | +does not have any mandatory building blocks. This functionality was previously available but was |
| 33 | +inadvertently blocked by an overly restrictive check. Imports are still correctly blocked for |
| 34 | +landing zones with mandatory building blocks due to technical limitations. |
| 35 | + |
| 36 | +### Fixed Building Block Execution Loop Issue |
| 37 | +**Audience:** User<br> |
| 38 | + |
| 39 | +#### Description |
| 40 | +We fixed an issue where some building blocks would get stuck for hours in a continuous loop of re-execution. This was caused by |
| 41 | +non-deterministic ordering of user roles and unnecessary tenant replications when platform tenant IDs were already set. |
| 42 | + |
| 43 | +#### How to use |
| 44 | +Building blocks that were previously stuck in execution loops will now run normally. You don't need to take any action - |
| 45 | +the fix is automatically applied to all existing building blocks. |
| 46 | + |
| 47 | +### Enable Editing Assignment Type for Building Block Outputs in Draft Mode |
| 48 | +**Audience:** User<br> |
| 49 | + |
| 50 | +#### Description |
| 51 | +We fixed an issue where you could not edit the assignment type of building block definition outputs when the |
| 52 | +definition version was in draft mode and not related to a custom platform. This is fixed now and you can always |
| 53 | +edit the assignment type for outputs when your building block definition is in draft mode. |
| 54 | + |
| 55 | +### Improved Terraform Variable Detection for Building Block Definitions |
| 56 | +**Audience:** User<br> |
| 57 | + |
| 58 | +#### Description |
| 59 | +We've enhanced the reliability of automatic variable detection when importing |
| 60 | +Terraform configurations into Building Block Definitions. Previously, certain |
| 61 | +complex Terraform expressions could cause parsing errors and prevent the |
| 62 | +system from properly detecting your variables. This improvement ensures that |
| 63 | +your Building Block Definitions work seamlessly, even when using advanced |
| 64 | +Terraform syntax. |
| 65 | + |
| 66 | +### Refresh Buttons for Building Block Lists |
| 67 | +**Audience:** User<br> |
| 68 | + |
| 69 | +#### Description |
| 70 | +We have added refresh buttons to the workspace building blocks and tenant building blocks overview pages. These |
| 71 | +buttons allow you to quickly refresh the building block list without having to reload the entire page. |
| 72 | + |
| 73 | +### Fix AWS Landing Zone Creation via Platform Builder |
| 74 | +**Audience:** User<br> |
| 75 | + |
| 76 | +#### Description |
| 77 | +Previously, when an AWS Landing Zone was created from within the Platform Builder, an error was |
| 78 | +displayed saying that awsEnrollAccount is a required property. This has been fixed. |
| 79 | + |
| 80 | +### Hide Building Blocks Without User Input From Creation Wizards |
| 81 | +**Audience:** User<br> |
| 82 | + |
| 83 | +#### Description |
| 84 | +Building blocks that don't require any user input are now automatically hidden from the project |
| 85 | +and tenant creation wizards. This streamlines the creation process by only showing building blocks |
| 86 | +that actually need configuration from users, reducing visual clutter and improving the overall user |
| 87 | +experience. |
| 88 | + |
| 89 | +### Workspace Building Block Preselected by Default during Definition Creation |
| 90 | +**Audience:** User<br> |
| 91 | + |
| 92 | +#### Description |
| 93 | +When creating a new building block definition, the Workspace Building Block |
| 94 | +type is now preselected by default instead of the Tenant Building Block type. |
| 95 | +This improves the onboarding experience as Workspace Building Block serves usually |
| 96 | +as the starting point for new platform teams. |
| 97 | + |
| 98 | +### Auto-select Current Workspace when Returning from meshStack Hub |
| 99 | +**Audience:** User<br> |
| 100 | + |
| 101 | +#### Description |
| 102 | +When you return to meshStack after browsing building block definitions in meshStack Hub, we now automatically |
| 103 | +pre-select your current workspace in the workspace picker. This eliminates the need to manually select your |
| 104 | +workspace in most cases, providing a smoother workflow when importing building block definitions from the Hub. |
| 105 | + |
| 106 | +### Fix GitHub Workflow Validation for Building Block Definition Purge Mode |
| 107 | +**Audience:** User<br> |
| 108 | + |
| 109 | +#### Description |
| 110 | +Fixed validation logic for GitHub workflow building block definitions when switching between deletion modes. |
| 111 | +The "Destroy Workflow" field is now correctly marked as optional when using "Purge in meshStack" mode, |
| 112 | +preventing validation errors that previously blocked form submission. |
| 113 | + |
| 114 | +### Improve Admin UI layout and extend app background |
| 115 | +**Audience:** User<br> |
| 116 | + |
| 117 | +#### Description |
| 118 | +This release contains a collection of UI updates and layout improvements that |
| 119 | +standardize the administration screens to the Control Plane UI layout and |
| 120 | +improves the main application background behavior. |
| 121 | + |
| 122 | +### Enable SSH Authentication for Terraform Modules in Building Blocks |
| 123 | +**Audience:** User<br> |
| 124 | + |
| 125 | +#### Description |
| 126 | +We now forward the configured SSH key (used to clone the primary Building Block repository) into the Terraform execution environment. |
| 127 | +This allows Terraform to fetch additional private modules (for example via git::ssh URLs) using the same key, without further configuration. |
| 128 | +No action is required; runs that previously failed with permission errors when downloading private modules should now succeed. |
| 129 | + |
| 130 | +### Improved Default View Toggle for Workspace Overview |
| 131 | +**Audience:** User<br> |
| 132 | + |
| 133 | +#### Description |
| 134 | +We redesigned the default view toggle functionality in the workspace overview to provide a better user experience. |
| 135 | +The toggle now shows more intuitive text that clearly indicates the current state and available action. When you |
| 136 | +switch from the new workspace overview back to the old view, we'll ask for your feedback to help us understand |
| 137 | +how we can improve the new experience. |
| 138 | + |
| 139 | +### Default Settings for Feature Previews |
| 140 | +**Audience:** User<br> |
| 141 | + |
| 142 | +#### Description |
| 143 | +Admins can now set default preferences for feature previews to streamline the user experience. You can configure |
| 144 | +feature previews to be enabled by default for new users and those who haven't made a decision yet, or clear |
| 145 | +default settings to let users opt-in individually. This helps platform teams control the default feature |
| 146 | +experience while respecting existing user preferences. |
| 147 | + |
| 148 | +### Fixed multiple scrollbars in Admin Area sidebar |
| 149 | +**Audience:** User<br> |
| 150 | + |
| 151 | +#### Description |
| 152 | +Resolved an issue where expanding all sidebar entries in the Admin Area resulted in two scrollbars appearing. Now only the sidebar content is scrollable, providing a cleaner and more intuitive user experience. |
| 153 | + |
0 commit comments