|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.1.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2024-12-18 to 2025-01-08 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* New MeshTenantUsageReport API Version |
| 10 | +* Fixes "Owner can not be removed" issue in Azure |
| 11 | +* Fixed Project Filtering Issue in Admin Panel Workspace View |
| 12 | +* Fix environmental usage reports with missing line items |
| 13 | +* Abort building block runs |
| 14 | +* Terraform Input Importer Works With Numbers |
| 15 | +* Building Block Definition Journey |
| 16 | +<!--truncate--> |
| 17 | + |
| 18 | +## Ticket Details |
| 19 | +### New MeshTenantUsageReport API Version |
| 20 | +**Audience:** Partner<br> |
| 21 | + |
| 22 | +#### Description |
| 23 | +With this release, we are introducing version 3 of meshTenantUsageReport API, providing additional |
| 24 | +fields and more detailed responses. meshTenantUsageReport API v3 also includes individual usage report |
| 25 | +line items grouped by seller and product group. Please be aware, that this new version is only supported |
| 26 | +if you are switched on to Chargeback 2.0. From March 1st 2025 on, meshTenantUsageReport API v2 will not be |
| 27 | +available at all anymore, see more information |
| 28 | +[here](https://docs.meshcloud.io/docs/meshcloud.chargeback-v2.html). |
| 29 | + |
| 30 | +### Fixes "Owner can not be removed" issue in Azure |
| 31 | +**Audience:** User<br> |
| 32 | + |
| 33 | +#### Description |
| 34 | +If a role was updated/swapped which was the last owner role assignment on an Azure Subscription |
| 35 | +this could lead to the "Owner can not be removed" error during replication. This has been fixed. |
| 36 | + |
| 37 | +### Fixed Project Filtering Issue in Admin Panel Workspace View |
| 38 | +**Audience:** User<br> |
| 39 | + |
| 40 | +#### Description |
| 41 | +When you click the "show projects" button in the admin panel workspace view the name instead of the workspace |
| 42 | +identifier was used for project filtering. This could lead to inconsistencies in the display of the project |
| 43 | +list and it has been fixed. |
| 44 | + |
| 45 | +### Fix environmental usage reports with missing line items |
| 46 | +**Audience:** Customer, Partner<br> |
| 47 | + |
| 48 | +#### Description |
| 49 | +For customers who already use the new chargeback 2.0 process, environmental |
| 50 | +tenant usage reports have not been successfully created in some cases. The |
| 51 | +tenant usage reports have included only a single zero-valued line item, even |
| 52 | +if the cloud provider had already provided the CO2 costs. This is now fixed. |
| 53 | +Only environmental usage reports (which are shown in the panel in the |
| 54 | +'GreenOps' section) that were created in the recent few months were impacted |
| 55 | +by this issue. |
| 56 | + |
| 57 | +### Abort building block runs |
| 58 | +**Audience:** Partner, Operator<br> |
| 59 | + |
| 60 | +#### Description |
| 61 | +Operators have now the possibility to abort runs that are pending |
| 62 | +or in progress. This can be achieved by navigating to the run details |
| 63 | +view within the admin area of the panel and click the 'Abort run' button. |
| 64 | +It is also possible to send a run update with the 'ABORTED' status via the |
| 65 | +meshObject API. The abort action will be accepted immediately but it can |
| 66 | +take a moment to come into effect. |
| 67 | + |
| 68 | +### Terraform Input Importer Works With Numbers |
| 69 | +**Audience:** User<br> |
| 70 | + |
| 71 | +#### Description |
| 72 | +This fixes a bug which prevented the detection of numeric defaults in the |
| 73 | +Terraform building block definition input importer. |
| 74 | + |
| 75 | +### Building Block Definition Journey |
| 76 | +**Audience:** User<br> |
| 77 | + |
| 78 | +#### Description |
| 79 | +We have introduced a guided visualization to help engineers understand |
| 80 | +the necessary steps for publishing a building block definition in the |
| 81 | +marketplace. This journey process is now available in the dedicated |
| 82 | +'Building Block Definition' general tab within the Service Management |
| 83 | +area. Engineers can follow this guidance from the initial setup until |
| 84 | +the definition is successfully published. |
| 85 | + |
0 commit comments