As a Platform Builder/Owner, I want the ability to hide certain Building Blocks from the Marketplace listing, so that users cannot discover or order them as standalone services.
Problem scope:
Many Building Block Definitions are created purely as components to be used within compositions (i.e. as a dependency of another Building Block), not for standalone/direct use. A standalone usage is often not intended because:
  • The Building Block has complex input requirements that only make sense when supplied by a parent/composing Building Block
  • It has input dependencies on other Building Blocks or context that an end user ordering it directly wouldn't be able to satisfy
  • Allowing direct orders could lead to misconfigured or broken instances, and support overhead
Currently, any defined Building Block is visible to all eligible workspaces in the Marketplace, with no way to mark it as "composition-only" / internal.
Desired outcome:
Building Block Definitions should support a visibility setting (e.g. "Hidden from Marketplace" / "Composition-only") that:
  • Prevents the Building Block from appearing in the Marketplace browsing/search view
  • Still allows the Building Block to be used as a dependency within other Building Block compositions
  • Does not affect already-provisioned instances of that Building Block (existing instances remain manageable)