Feature Requests

As an workspace owner I want to move projects from one customer to another customer

As a platform engineer I want meshStack to delete actual cloud resources. At the moment I still have to manually check and possibly delete these resources but I'd rather hand out that responsibility to meshStack.

Landing Zone parameters can't be changed. As a workaround, you can remove the "disabled" html attribute via developer tools.

As an application team I want to add building blocks to my tenants via API to fully automate the creation of a new environment.

As a Cloud Foundation admin, I need to have the automatic deletion of Tenants from the cloud once I've deleted them from meshStack to reduce manual work and prevent running but not-used resources.

As a Platform Engineer I would like to easily rotate platform secrets and thereby reduce the risk of compromised secrets.

I have integrated a custom platform using building blocks. The building block that manages the permissions on the tenant uses the "User Permission" input source. On the first creation, this works as expected. However, the permissions on projects are managed in self-service by application teams. And after updating permissions, application teams expect that those permissions are also replicated to the tenant (similarly to how it's done for AWS/GCP/Azure/...).

At the moment, the panel asks for an existing workspace and project for adopting tenants. Since meshStack does not allow to create projects without any tenants, this means I have to create a project outside of the wizard with a tenant I actually wouldn't need. The wizard should allow me to create a project.

For a meshRole (e.g. "ProjectAdmin") you can define multiple roles in GCP, so that a user that has "ProjectAdmin" has mutiple roles assigned in GCP. We would like to have the same feature for Azure. Background: We don't want to use the "Contributor" role in Azure, which has too many rights. On the other hand we don't want to use custom roles as you have to keep them up-to-date when Microsoft releases new features / permissions. We want to use the smaller build-in roles in Azure and put them together to a meshRole for easier management.

As a cloud foundation admin, I want to adopt tenants from within the panel instead of using the meshObject API. Because I need to specify a customer and a project for the tenant, we would need an input mask. Ideally, the wizard would print a meshObject API command after I have imported a tenant. This way I can gradually move from importing tenants via the panel to using the API if I want to do a bulk import.