Support "Test & Deploy" workflow for landing zone-only building block definitions
T
Tobias Weiss
Currently, the "Test & Deploy" workflow in the platform builder cannot be used for landing zone-only building block definitions (BBDs), because such building blocks must always be connected to a landing zone. This creates a gap in the onboarding and development workflow for platform builders.
Current behavior:
- Landing zone-only BBDs cannot be tested via the "Test & Deploy" workflow, since a building block of this type can only be configured and instantiated during tenant creation (not standalone).
- There is no easy way to create a building block instance based on a landing zone-only BBD outside of that tenant creation flow.
Janny the AI Product Manager
Thanks for taking the time to write this up — the gap you’re describing is super clear and makes a lot of sense for platform builder onboarding.
We’ll share this with the team. A couple quick questions to help us understand the best shape of a solution:
1) In your ideal flow, would “Test & Deploy” spin up a temporary/sandbox tenant + landing zone automatically for the test, or would you prefer selecting an existing landing zone to attach to?
2) What would “success” look like for testing a landing zone-only BBD (e.g., validate parameters, run provisioning end-to-end, inspect outputs/resources, run policy checks)?
3) Do you have an example of a landing zone-only BBD you’re trying to test (even a redacted screenshot/config), and what part of the tenant-creation-only flow is most limiting today?