|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.38.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-08-27 to 2025-09-03 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Workload Identity Federation Configuration Security Enhancement |
| 10 | +* Remove expansion option for Building Block Steps if no further details available |
| 11 | +* Fixed Building Block Definition Parent Selection in Platform Builder |
| 12 | +* Updated color theme in meshPanel |
| 13 | +* Move Marketplace Pricing Information to a Dedicated Card Element |
| 14 | +* Return HTTP 401 When Token Decoding Fails |
| 15 | +* Rate Limiting for meshObject API Endpoints |
| 16 | +* Increase Email Signature Character Limit |
| 17 | +* Display Platform UUID in Platform Control Plane |
| 18 | +* Terraform Building Blocks With Nested Inputs/Outputs |
| 19 | +* Enable Hierarchical Organizational Unit Assignments for AWS |
| 20 | +* Enable Hierarchical Management Group Assignments for Azure |
| 21 | +* meshStack Copilot "Get Help" Button For Platform Description Fields |
| 22 | +* Improved Tenant Identification in meshPanel |
| 23 | +<!--truncate--> |
| 24 | + |
| 25 | +## Ticket Details |
| 26 | +### Workload Identity Federation Configuration Security Enhancement |
| 27 | +**Audience:** User<br> |
| 28 | + |
| 29 | +#### Description |
| 30 | +Workload Identity Federation (WIF) configuration details are now fetched securely from an authenticated endpoint |
| 31 | +instead of being exposed in the browser environment. This improves security by ensuring that WIF |
| 32 | +configuration data like issuer URLs, audiences, and thumbprints are only accessible to authenticated users. |
| 33 | + |
| 34 | +### Remove expansion option for Building Block Steps if no further details available |
| 35 | +**Audience:** User<br> |
| 36 | + |
| 37 | +#### Description |
| 38 | +Being able to expand steps that did not contain any additional information was confusing before. Therefore the expansion option was now removed for those cases. |
| 39 | + |
| 40 | +### Fixed Building Block Definition Parent Selection in Platform Builder |
| 41 | +**Audience:** User<br> |
| 42 | + |
| 43 | +#### Description |
| 44 | +We fixed an issue where child building blocks definitions could not properly select their parent |
| 45 | +building block definitions in the platform builder area when the parent belonged to a different workspace. |
| 46 | + |
| 47 | +### Updated color theme in meshPanel |
| 48 | +**Audience:** User<br> |
| 49 | + |
| 50 | +#### Description |
| 51 | +We have updated the color theme in meshPanel to provide a more modern and consistent visual experience. |
| 52 | +The changes improve the overall look and feel of the interface while maintaining readability and accessibility. |
| 53 | + |
| 54 | +### Move Marketplace Pricing Information to a Dedicated Card Element |
| 55 | +**Audience:** User<br> |
| 56 | + |
| 57 | +#### Description |
| 58 | +The pricing information in marketplace service details has been moved from the main content area |
| 59 | +to a dedicated card on the right side of the page. |
| 60 | + |
| 61 | +### Return HTTP 401 When Token Decoding Fails |
| 62 | +**Audience:** User<br> |
| 63 | + |
| 64 | +#### Description |
| 65 | +The API now returns a proper HTTP 401 Unauthorized response when token decoding fails, |
| 66 | +instead of a HTTP 500 Internal Server Error. This improves error handling and provides |
| 67 | +clearer feedback to you when authentication fails due to invalid tokens. |
| 68 | + |
| 69 | +### Rate Limiting for meshObject API Endpoints |
| 70 | +**Audience:** User<br> |
| 71 | + |
| 72 | +#### Description |
| 73 | +We are currently evaluating rate limiting for meshObject API read endpoints in QA environments to improve system stability and prevent abuse. |
| 74 | +The rate limits are applied to the meshObject API endpoints. |
| 75 | +This feature helps ensure fair resource usage across all API consumers and maintains consistent performance under high load conditions. |
| 76 | +We plan to roll out this feature to production environments in the upcoming week. |
| 77 | + |
| 78 | +#### How to use |
| 79 | +Once enabled in production, rate limits will automatically be applied to meshObject API endpoints with default limits of 2 concurrent |
| 80 | +requests per user and 80 requests per minute in total per endpoint. API responses will include HTTP 429 (Too Many Requests) status codes when limits are exceeded. |
| 81 | +No configuration changes will be required on your end - the limits are designed to accommodate normal usage patterns while protecting |
| 82 | +against excessive usage. |
| 83 | +If you need higher limits please contact our support. |
| 84 | + |
| 85 | +### Increase Email Signature Character Limit |
| 86 | +**Audience:** Customer<br> |
| 87 | + |
| 88 | +#### Description |
| 89 | +This change increases the character limit for the email signature field from 200 to 500 characters, allowing for more detailed signatures. |
| 90 | + |
| 91 | +### Display Platform UUID in Platform Control Plane |
| 92 | +**Audience:** User<br> |
| 93 | + |
| 94 | +#### Description |
| 95 | +The platform control plane in meshPanel now displays the |
| 96 | +meshStack Platform ID (UUID) alongside other platform |
| 97 | +information. This provides platform operators with a |
| 98 | +direct way to access the unique identifier for their |
| 99 | +platform, which is useful for API operations and |
| 100 | +troubleshooting. |
| 101 | + |
| 102 | +### Terraform Building Blocks With Nested Inputs/Outputs |
| 103 | +**Audience:** Operator<br> |
| 104 | + |
| 105 | +#### Description |
| 106 | +When creating a Terraform building block definition inputs and outputs are automatically imported from Git. |
| 107 | +To simplify the process, meshStack will ignore inputs and outputs found in subdirectories, as they are not directly relevant to the building block. |
| 108 | + |
| 109 | +### Enable Hierarchical Organizational Unit Assignments for AWS |
| 110 | +**Audience:** User<br> |
| 111 | + |
| 112 | +#### Description |
| 113 | +AWS platforms now support hierarchical organizational unit assignment for accounts. When enabled, accounts |
| 114 | +can be placed in child organizational units below the organizational unit defined in the landing zone, allowing for more |
| 115 | +granular and flexible account organization within the AWS Organizations hierarchy. |
| 116 | + |
| 117 | +#### How to use |
| 118 | +Platform operators can enable this feature by configuring the "Allow Hierarchical Organizational Unit Assignment" |
| 119 | +setting in the AWS platform configuration. When enabled, accounts living in an organizational unit below |
| 120 | +the one defined in the landing zone will remain in their current organizational unit. This provides greater flexibility |
| 121 | +for organizing accounts in complex AWS Organizations structures while maintaining proper governance. |
| 122 | + |
| 123 | +### Enable Hierarchical Management Group Assignments for Azure |
| 124 | +**Audience:** User<br> |
| 125 | + |
| 126 | +#### Description |
| 127 | +Azure platforms now support hierarchical management group assignment for subscriptions. When enabled, subscriptions |
| 128 | +can be placed in child management groups below the management group defined in the landing zone, allowing for more |
| 129 | +granular and flexible subscription organization within the Azure management hierarchy. |
| 130 | + |
| 131 | +#### How to use |
| 132 | +Platform operators can enable this feature by configuring the "Allow Hierarchical Management Group Assignment" |
| 133 | +setting in the Azure platform configuration. When enabled, subscriptions living in a management group below |
| 134 | +the one defined in the landing zone will remain in their current management group. This provides greater flexibility |
| 135 | +for organizing subscriptions in complex Azure management group structures while maintaining proper governance. |
| 136 | + |
| 137 | +### meshStack Copilot "Get Help" Button For Platform Description Fields |
| 138 | +**Audience:** User<br> |
| 139 | + |
| 140 | +#### Description |
| 141 | +A new "Get Help" copilot button has been added to platform description input fields during both platform creation and |
| 142 | +platform editing. This button provides contextual assistance for writing effective platform descriptions. When clicked, |
| 143 | +it opens copilot with a pre-filled message suggesting how to create a meaningful platform description. |
| 144 | + |
| 145 | +### Improved Tenant Identification in meshPanel |
| 146 | +**Audience:** User<br> |
| 147 | + |
| 148 | +#### Description |
| 149 | +We have improved how tenant identifiers are displayed throughout meshPanel to provide clearer distinction between |
| 150 | +different types of tenant IDs. The tenant control plane now clearly shows the "meshStack Tenant ID" (UUID), |
| 151 | +"Platform Tenant ID" (cloud platform specific ID), and "Tenant name" separately. This makes it easier for you |
| 152 | +to understand and work with tenant identifications, especially when using APIs or troubleshooting tenant-related |
| 153 | +issues. |
| 154 | + |
0 commit comments