|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2024.53.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2024-12-02 to 2024-12-04 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Fixes Azure Replication With Certain Role Config |
| 10 | +* Fix Failing Tag Definition Update with Default Value |
| 11 | +* Set API Key Expiration Date Limit |
| 12 | +* CSV Export for Chargeback 2.0 |
| 13 | +<!--truncate--> |
| 14 | + |
| 15 | +## Ticket Details |
| 16 | +### Fixes Azure Replication With Certain Role Config |
| 17 | +**Audience:** User<br> |
| 18 | + |
| 19 | +#### Description |
| 20 | +This fixes a regression that could cause Azure replications to fail if you had the same Azure role |
| 21 | +mapped to multiple roles in meshStack. |
| 22 | + |
| 23 | +### Fix Failing Tag Definition Update with Default Value |
| 24 | +**Audience:** Partner<br> |
| 25 | + |
| 26 | +#### Description |
| 27 | +In certain cases, when you update the definition of a single-select tag with a default value, you may encounter an error. This issue has now been fixed. |
| 28 | + |
| 29 | +### Set API Key Expiration Date Limit |
| 30 | +**Audience:** Partner, Customer<br> |
| 31 | + |
| 32 | +#### Description |
| 33 | +As an admin, you can now define a maximum expiration period, and users will be required to set their API key expirations within that timeframe. This helps you maintain control over key lifetimes. |
| 34 | + |
| 35 | +### CSV Export for Chargeback 2.0 |
| 36 | +**Audience:** Partner, Customer<br> |
| 37 | + |
| 38 | +#### Description |
| 39 | +The CSV export of chargeback statements is now available for the Chargeback 2.0 process. |
| 40 | +It retains the same structure as the CSV export from the previous chargeback process. |
| 41 | +This export includes only the updated cost data, ensuring the report reflects the latest information, |
| 42 | +such as late bills from providers. |
| 43 | + |
0 commit comments