develop

docs/meshcloud.platforms.md

@@ -3,7 +3,7 @@ id: meshcloud.platforms
 title: meshPlatforms
 ---
 
-At the heart of a meshcloud are the cloud platforms that provide cloud services and resources to users.
+At the heart of a meshStack are the cloud platforms that provide cloud services and resources to users.
 
 ## meshPlatforms
 
@@ -12,13 +12,13 @@ The following terms relate to cloud platforms:
 - platform-type describes the type of a cloud platform, e.g. OpenStack, Cloud Foundry or AWS.
 - meshPlatform to describe a particular deployment of such a cloud platform.
 
-For example, meshstack can manage two, fully isolated OpenStack deployments located in different
+For example, meshStack can manage two, fully isolated OpenStack deployments located in different
 regions in the same meshcloud. While they are both of the same platform-type OpenStack, they each
 are individual meshPlatforms.
 
 ## meshLocations
 
-In a meshcloud, cloud meshPlatforms can be grouped by **meshLocation**.
+In a meshStack, cloud meshPlatforms can be grouped by **meshLocation**.
 Locations are free-form but they are typically used to help users identify the geographic datacenter
 location as well as identify the party that is responsible for managing the cloud meshPlatforms
 in this meshLocation. For example, this could be an internal IT division that manages private clouds or

docs/meshstack.azure.landing-zones.md

@@ -131,6 +131,10 @@ The meshProject roles must be mapped to Azure specific roles. You can control th
 
 The Azure Role Definition is the RBAC ID of the Azure role you want to use. You can either create your own roles or use the [predefined global IDs](https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles) from Azure.
 
+If you like you can also add an ABAC condition to role assignments done by meshStack as part of the role mapping configuration.
+Azure allows for all kinds of advanced conditions on these role assignments.
+For more information on this topic please refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/role-based-access-control/conditions-overview).
+
 ### Azure Function Invocation
 
 Platform Operators can configure an Azure Function invocation to trigger a small piece of code in the cloud whenever meshStack's replicator reconciliates the Landing Zone definition against the Subscription. Currently this function is invoked via a `POST` request and receives parameters from meshStack via HTTP header values.

website/blog/2025-01-29-Release-0.md

@@ -0,0 +1,103 @@
+---
+author: meshcloud
+title: Release 2025.4.0
+---
+
+Release period: 2025-01-22 to 2025-01-29
+
+This release includes the following issues:
+* Non Admin Users Can Not Modify Locations Anymore
+* Enhancements to Building Block Definition Creation
+* Revised access control search
+* Fix Boolean Building Block Inputs
+* Remove unassigned users from notification recipients
+* API key row alignment
+* Adding Access Request Rejected to Event Logs
+* Merge Building Block Menus into One
+* Fix SCIM Group Deletion
+* API Key read-only Permissions for Workspaces
+* Remove Project Deletion Queue
+<!--truncate-->
+
+## Ticket Details
+### Non Admin Users Can Not Modify Locations Anymore
+**Audience:** User<br>
+
+#### Description
+As locations are potentially shared between different platform instances the edit right for regular users 
+was removed. Locations can now only be edited by admins from the admin area.
+
+### Enhancements to Building Block Definition Creation
+**Audience:** User<br>
+
+#### Description
+In this release, we enhanced the General tab of the Building Block Definition creation interface. And we added a new input field that 
+allows you to select the type of building block. This marks an important step toward supporting workspace building blocks in the future.
+At this stage, you can select only tenant building blocks.
+
+### Revised access control search
+**Audience:** User<br>
+
+#### Description
+In recent weeks, we have added the ability to search for users/groups 
+within the access control screens. This change may cause unexpected 
+validation errors. The view has been revised and made more robust.
+
+### Fix Boolean Building Block Inputs
+**Audience:** Operator<br>
+
+#### Description
+When editing building block inputs of type boolean, the default 
+value was displayed instead of the actual value in some cases. This is now fixed.
+
+### Remove unassigned users from notification recipients
+**Audience:** User, Customer, Partner, Operator<br>
+
+#### Description
+Previously, there were occurrences where users removed from a workspace were still
+receiving notifications. Now, users removed from a workspace are periodically cleaned up
+from the notification recipients list. This ensures that only users with access to a workspace 
+are notified.
+
+### API key row alignment
+**Audience:** User<br>
+
+#### Description
+We have resolved the alignment of the API key overview rows within the workspace control 
+plane. The offset within rows has been resolved. The columns now match the row values again.
+
+### Adding Access Request Rejected to Event Logs
+**Audience:** Customer<br>
+
+#### Description
+Previously when 4-eyes principle was enabled, in rare cases no events were written when an access request to a workspace was rejected. This issue has been resolved, and access request rejected events are now consistently logged.
+
+### Merge Building Block Menus into One
+**Audience:** User<br>
+
+#### Description
+For a long time there were two menu items in the Admin Area & Service Management Area for managing building blocks
+and their definitions. We now merged these two menus and pages into one. This should make it easier to find what
+you are looking for.
+
+### Fix SCIM Group Deletion
+**Audience:** Customer<br>
+
+#### Description
+Previously, when you attempted to delete a group via SCIM that is assigned to one or more workspaces, an error occurred, preventing the action from completing successfully. This issue has been fixed.
+
+### API Key read-only Permissions for Workspaces
+**Audience:** Partner, User<br>
+
+#### Description
+Users can now add a new permission to API Keys to read the workspace that owns the API key from meshObject API.
+Admins can add a new admin permissions to API Keys that grants access to list all workspaces.
+
+### Remove Project Deletion Queue
+**Audience:** User<br>
+
+#### Description
+We have removed the project deletion queue which could be found in the workspace overview under projects -> Deletion Queue.
+A while back we introduced visibility of projects that are awaiting deletion directly in the project overview.
+This made the deletion queue redundant and we have now removed it.
+

website/static/api/api_index.html

@@ -549,12 +549,12 @@ <h3 id="_index">Index</h3>
 
 {
   "_links" : {
-    "meshobjects" : {
-      "href" : "https://mesh-backend-url/api/meshobjects"
-    },
     "metadata" : {
       "href" : "https://mesh-backend-url/api/metadata"
     },
+    "meshobjects" : {
+      "href" : "https://mesh-backend-url/api/meshobjects"
+    },
     "self" : {
       "href" : "https://mesh-backend-url/api"
     }
@@ -566,7 +566,7 @@ <h3 id="_index">Index</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-01-22 14:03:42 UTC
+Last updated 2025-01-29 13:37:34 UTC
 </div>
 </div>
 </body>

website/static/api/api_key_login.html

@@ -591,7 +591,7 @@ <h3 id="api_key_login">API Key Login</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-01-22 14:03:42 UTC
+Last updated 2025-01-29 13:37:34 UTC
 </div>
 </div>
 </body>

website/static/api/api_keys.html

@@ -477,7 +477,7 @@ <h3 id="api_keys">API Keys</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-01-22 14:03:42 UTC
+Last updated 2025-01-29 13:37:34 UTC
 </div>
 </div>
 </body>

website/static/api/common_data_formats.html

@@ -542,7 +542,7 @@ <h3 id="tags">Tags</h3>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2025-01-22 14:03:42 UTC
+Last updated 2025-01-29 13:37:34 UTC
 </div>
 </div>
 </body>