Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

develop #802

Merged
merged 3 commits into from
May 15, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/assets/OrgStructure.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/assets/landingZone.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
7 changes: 5 additions & 2 deletions docs/meshstack.index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,12 @@ It is NOT a meta-layer across clouds. Users access native cloud APIs for their d

## Central Concepts

meshStack uses the concepts of Workspaces and Projects to represent the structure of existing application teams in the meshStack platform. Application Team can manage Tenants inside Projects. In order to reflect the organization's compliance and security standards in the cloud a Landing Zone is applied to every Tenant. Building Blocks can be leveraged either as part of a modular Landing Zone or additionally on top of a Tenant. Building Blocks are deployed based on the configuration provided in the Building Block definition.
meshStack uses the concepts of Workspaces and Projects to represent the structure of existing application teams in the meshStack platform. Application Team can manage Tenants inside Projects.
![meshModel](assets/OrgStructure.png)

In order to reflect the organization's compliance and security standards in the cloud a Landing Zone is applied to every Tenant. Building Blocks can be leveraged either as part of a modular Landing Zone or additionally on top of a Tenant. Building Blocks are deployed based on the configuration provided in the Building Block definition.
meshStack supports the management of multiple platforms of the same or different type. Below you can see an overview of the relations between the individual elements in meshStack as objects.
![meshModel](assets/meshModel.png)
![landingZones](assets/landingZone.png)

## Integrations

Expand Down
78 changes: 78 additions & 0 deletions website/blog/2024-05-15-Release-0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
---
author: meshcloud
title: Release 2024.22.0
---

Release period: 2024-05-08 to 2024-05-15

This release includes the following issues:
* Fix deprecated Building Block Definitions
* Landing zone-only definitions not shown in Marketplace
* Lenient parsing of OpenStack catalogs
* Improved Tags Layouts with Hover-Activated Overflow
* Define Policies from Workspace to Landing Zone
* Better replication remarks for users without an EUID
* Manage your API Keys from within your workspace
* Manage projects with API Keys
<!--truncate-->

## Ticket Details
### Fix deprecated Building Block Definitions
**Audience:** User<br>

#### Description
Previously, Building Block Definitions owned by a workspace with several published versions were incorrectly shown as deprecated. Now, they are accurately displayed as published.

### Landing zone-only definitions not shown in Marketplace
**Audience:** User<br>

#### Description
Building Block Definitions marked as 'Use in Landing Zones only' were erroneously accessible in the Marketplace via the "Related to" section of a Platform. This allowed users to select and book these definitions without the required landing zone, contrary to their intended use. This issue has been fixed.

### Lenient parsing of OpenStack catalogs
**Audience:** Operator<br>

#### Description
When configuring OpenStack, operators have a lot of freedom to configure catalog entries.
We fixed an error where meshStack failed to parse catalogs containing unexpected "interface"
values for a catalog entry.

### Improved Tags Layouts with Hover-Activated Overflow
**Audience:** User<br>

#### Description
In this release, we've resolved container overflow issues caused by long tag values. Now, our application
displays approximately three tag values visibly, with the remaining tags shown when hovered over. This
enhancement ensures improved readability and user experience, addressing concerns about disrupted layouts
and extended content beyond screen boundaries.

### Define Policies from Workspace to Landing Zone
**Audience:** Partner<br>

#### Description
It is now also possible to define a Policy from Workspace to Landing Zone. A good example for
such a policy is e.g. a policy for a matching Business Unit on your Workspaces and Landing Zones.
That way, you can restrict certain Landing Zones to only Workspaces that belong to a certain Business Unit.

### Better replication remarks for users without an EUID
**Audience:** User<br>

#### Description
Users whose EUID is missing, can not be added to a platform tenant. But previously
the error replication remark was not consistent and on rare occasions could be missing.
This has been fixed.

### Manage your API Keys from within your workspace
**Audience:** Customer<br>

#### Description
API Keys for their own workspace can now be managed by Workspace Owners and Workspace Managers.
Navigate to the 'API Keys' sub tab within the 'Workspace Access' tab on the Workspace Control Plane to do so.

### Manage projects with API Keys
**Audience:** User<br>

#### Description
You can now use your API Keys to manage (create, update, delete) projects
within your workspace. More objects will be supported soon.

Loading