J
member badge
Johannes Rudolph
As a platform engineer managing my internal developer platform as code, I want to configure recurring prices for my Building Block Definitions and Platforms (Tenant Fees) via the meshObject API — so I can keep pricing configuration in version control alongside my platform definitions, automate price changes across environments, and avoid manual UI steps.
Current Situation
meshStack supports setting prices for Building Block Definitions and Platforms (Tenant Fees) via the meshPanel UI today. However, these prices cannot be defined or updated via the meshObject API or Terraform provider.
This means:
  • When automating platform setup end-to-end (e.g., via CI/CD or Terraform), pricing must still be configured manually in the UI
  • Pricing is disconnected from the rest of your platform IaC configuration (meshBuildingBlockDefinition, meshPlatform, meshLandingZone)
Requested Capability
Expose pricing configuration via the meshObject API for:
  • Building Block Definitions
    (
    meshBuildingBlockDefinition
    ): include a
    spec.prices
    field supporting recurring fees (hourly/daily/monthly) with currency and amount
  • Platforms (Tenant Fees)
    (
    meshPlatform
    ): include a
    spec.tenantFee
    or
    spec.prices
    field supporting recurring tenant fees per platform
This would allow platform engineers to fully configure their service catalog as code and automate the entire platform setup lifecycle without UI interaction.
Note: The pricing could also be exposed as a separated product catalog API, i.e. setting up pricing is separate from setting up the building block/platform itself. However this should allow for a clear workflow from terraform.
Related Requests
Contact our customer success team or support@meshcloud.io if you have questions.