Tag validation via API changes
in progress
R
Rebecca
Currently, when meshObjects are created via API users from the admin area, it is possible to bypass policy checks, allowing the creation of objects that may not comply with defined policies or contain unsupported tag values.
In the future, I would like to enable validation for admin-initiated API requests as well, ensuring that all meshObjects—regardless of how they are created—are consistently validated and compliant with meshStack policies.
J
Johannes Rudolph
marked this post as
in progress
We are currently rolling out this feature across API endpoints.
Release 2025.47.0 (October 29, 2025): meshWorkspaces and meshProjects
Release 2025.50.0 (Nov 19, 2025): meshBuildingBlockDefinitions, meshPaymentMethods, meshLandingZones, meshProjectRoles
You can activate the new validation mode via Admin Area -> Settings -> Compliance ->Tags.
We recommend customers adopt this new validation mode as soon as possible, as the validation bypass behavior will be deprecated. Please see https://feedback.meshcloud.io/deprecations/p/deprecation-bypassing-tag-validation-in-admin-api-calls for the deprecation of the legacy behavior.
J
Johannes Rudolph
marked this post as
in progress
We are currently rolling out this feature across API endpoints.
Release 2025.47.0 (October 29, 2025): meshWorkspaces and meshProjects
Release 2025.50.0 (Nov 19, 2025): meshBuildingBlockDefinitions, meshPaymentMethods, meshLandingZones, meshProjectRoles
You can activate the new validation mode via Admin Area -> Settings -> Compliance ->Tags.
We recommend customers adopt this new validation mode as soon as possible, as the validation bypass behavior will be deprecated. Please see https://feedback.meshcloud.io/deprecations/p/deprecation-bypassing-tag-validation-in-admin-api-calls for the deprecation of the legacy behavior.