|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.8.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-02-24 to 2025-02-26 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Test Connection & Auto Import for Terraform Building Blocks |
| 10 | +* Fix sorting of Usage Reports and Chargeback Statements |
| 11 | +* Admin permissions for API Keys to manage Service Instances |
| 12 | +* Fixed HTTP response status codes for meshServiceInstance API |
| 13 | +* Re-enable Access to old Projects with Invalid Deletion State |
| 14 | +* Don't show deleted OSB Plans in Marketplace |
| 15 | +* Fix Forecast for Unused Payment Methods |
| 16 | +* Moved Building Block Supported Platforms |
| 17 | +* Test connection and import for Terraform Building Blocks |
| 18 | +<!--truncate--> |
| 19 | + |
| 20 | +## Ticket Details |
| 21 | +### Test Connection & Auto Import for Terraform Building Blocks |
| 22 | +**Audience:** User<br> |
| 23 | + |
| 24 | +#### Description |
| 25 | +When creating a Terraform building block in the UI, you can now test the connection to the target |
| 26 | +git repository and automatically import all Terraform inputs & outputs. Please note that for |
| 27 | +the time being this is only supported for public git providers GitHub, GitLab, Azure DevOps & Bitbucket. |
| 28 | +Self-hosted variants are not supported at the moment. |
| 29 | + |
| 30 | +#### How to use |
| 31 | +When entering a valid repository URL in the Terraform building block creation form, a new button will |
| 32 | +appear called "Test Connection". You can click this button to test the connection to the repository. |
| 33 | +When landing on the "Inputs" part of the creation form, you will then be prompted to decide which |
| 34 | +inputs & outputs to import. |
| 35 | + |
| 36 | +### Fix sorting of Usage Reports and Chargeback Statements |
| 37 | +**Audience:** Partner, Customer<br> |
| 38 | + |
| 39 | +#### Description |
| 40 | +When further pages of usage reports or chargeback statements were loaded, the sorting was not applied correctly |
| 41 | +on the further pages. This fix ensures that the sorting is maintained when further pages are loaded. |
| 42 | + |
| 43 | +### Admin permissions for API Keys to manage Service Instances |
| 44 | +**Audience:** Partner<br> |
| 45 | + |
| 46 | +#### Description |
| 47 | +This release adds new admin permissions for API keys to manage Service Instances across all workspaces. |
| 48 | +Regular permissions for managing Service Instances within the API key's workspace remain available. |
| 49 | + |
| 50 | +### Fixed HTTP response status codes for meshServiceInstance API |
| 51 | +**Audience:** Partner<br> |
| 52 | + |
| 53 | +#### Description |
| 54 | +We have made a minor fix to HTTP response status codes returned by the meshObject API |
| 55 | +endpoints for meshServiceInstance when submitting a duplicate service instanceId. |
| 56 | +Please review the details of this release note for the specific changes. |
| 57 | + |
| 58 | +#### How to use |
| 59 | +The API operation POST /api/meshobjects/meshServiceInstances now returns a 409 status |
| 60 | +code when a meshServiceInstance with the same instanceId already exists. |
| 61 | +Previously, the operation returned a HTTP 500 status code for this case. |
| 62 | + |
| 63 | +Please note that this change is introduced without an explicit change in the API version for this endpoint |
| 64 | +because we consider this to be a bug fix. |
| 65 | + |
| 66 | +### Re-enable Access to old Projects with Invalid Deletion State |
| 67 | +**Audience:** Customer<br> |
| 68 | + |
| 69 | +#### Description |
| 70 | +If a tenant deletion was rejected by a platform operator in August or September 2024, the project did |
| 71 | +not become active again after the rejection. The affected projects are now active again and can be |
| 72 | +accessed by the application teams. Only a very little amount of projects were affected by this issue. |
| 73 | + |
| 74 | +### Don't show deleted OSB Plans in Marketplace |
| 75 | +**Audience:** Partner, Customer<br> |
| 76 | + |
| 77 | +#### Description |
| 78 | +Deleted OSB service plans were included in the internal pricing section of a service in the Marketplace. The |
| 79 | +deleted plans are now not shown anymore for the internal pricing section as intended. |
| 80 | + |
| 81 | +### Fix Forecast for Unused Payment Methods |
| 82 | +**Audience:** Partner, Customer<br> |
| 83 | + |
| 84 | +#### Description |
| 85 | +Previously, the forecast in the payment method graph (i.e., the dotted line) |
| 86 | +sometimes indicated a cost increase for payment methods that have already |
| 87 | +been replaced by a different payment method. This has been fixed now, so that |
| 88 | +the dotted line remains flat to correctly indicate that no further costs are |
| 89 | +expected for this payment method. |
| 90 | + |
| 91 | +### Moved Building Block Supported Platforms |
| 92 | +**Audience:** User<br> |
| 93 | + |
| 94 | +#### Description |
| 95 | +To streamline the Building Block configuration process, we have moved the Supported Platforms selection from the Implementation step to the |
| 96 | +General step, directly grouped with the Building Block Type selection if a Tenant Building Block is selected. |
| 97 | + |
| 98 | +### Test connection and import for Terraform Building Blocks |
| 99 | +**Audience:** Operator<br> |
| 100 | + |
| 101 | +#### Description |
| 102 | +You can now test your connection to your SSH & HTTPS git repository for Terraform Building Blocks |
| 103 | +and optionally import your inputs and outputs directly from the detected Terraform files. |
| 104 | +Please note that this is currently only supported for cloud-hosted instances of GitHub, GitLab, |
| 105 | +BitBucket and Azure DevOps. Self-hosted git providers are not supported at this time. |
| 106 | + |
0 commit comments