PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Infrastructure
Infra Deployments Management & Scaling Virtual Machines

Infrastructure Deployments

An Infrastructure Deployment provisions or updates the cloud resources exposed by the selected Biztraak project and provider workflow. Depending on that workflow, this may include networking, IAM, secrets, databases, storage, or other infrastructure.

Depending on the selected workflow, infrastructure deployments may use a separate Terraform execution path rather than the component’s code pipeline. Review the provider workflow before assuming that infrastructure and application changes share the same pipeline.

How Infra Deployments Work

  1. Trigger

    • Start an infra deployment from the project UI or API.
    • Select from the service providers and regions exposed by the component workflow.

  2. Execution

    • Biztraak runs Terraform-based deployment scripts inside a secure, isolated runner.
    • Execution records and logs are available according to the selected workflow.

  3. Provisioning

    • Resources like VPCs, IAM roles, secrets, and storage are created in your cloud accounts.
    • Non-secret outputs such as IDs, URLs, and endpoints may be surfaced in the UI. Protected values must remain in the platform’s protected configuration path.

Dependencies Between Components

Deployments in Biztraak follow an inherent dependency tree:

  • Workflow-specific foundation

    • A workflow that provisions a shared foundation may create the Organization, VPC, IAM roles, storage buckets, and logging resources.
    • When the selected workflow includes Canvas integration, those resources can appear as visible components there.
    • Deploy from Repo does not necessarily perform this complete sequence. Its resources and outputs depend on the selected provider workflow.

  • Outputs Flow Downstream

    • When the selected workflow exposes downstream outputs, one component can provide values to dependent components.
    • Example: a database connection string may be injected into API service environment variables.
    • Example: a storage bucket URL may be passed to a frontend as a resource variable.

  • Env Variables

    • The selected workflow determines whether values can be used by infrastructure, code deployments, or both.
    • Build-time and runtime injection depend on the selected workflow.
    • Central management and cross-environment consistency depend on the configured deployment path.

The dependency model helps make ordering and relationships visible, but the selected provider workflow remains responsible for the actual resources, outputs, and readiness checks.

Managing Infra Deployments

  • Script Management

    • Script editing and version history depend on the workflow that exposes the infrastructure definition.
    • If Git-backed infrastructure is not available for your workflow, use the editor and change history exposed by the product.

  • Future: Git-Backed Infra

    • Git-backed scripts and enterprise repository integration are planned capabilities, not a default infrastructure workflow.

Features

  • Secure Execution: isolated runners for infra.
  • Provider-specific: use the provider paths exposed by the selected workflow.
  • Dependency-Aware: selected workflows may expose an Org → VPC → Storage → App dependency chain with the related outputs wired together.
  • Auditable: logs, outputs, and dependencies tracked.
  • Git-backed templates: available only where the selected workflow exposes repository-backed infrastructure definitions.

Why Separate from Code?

  • Infra First: code deployments rely on infra existing.
  • Dependencies Matter: outputs flow between components automatically when the selected workflow exposes those outputs.
  • Faster Iteration: split pipelines = fast app builds, stable infra provisioning.

Example Foundation Workflow

The following is a workflow-specific example. It does not describe guaranteed behavior for every Deploy from Repo project.

  1. User selects a workflow that provisions an API service and its shared foundation.
  2. Biztraak may provision:
    • Org + VPC (if missing).
    • IAM roles + permissions.
    • Storage + logging buckets.
  3. The API is deployed on top of that infrastructure when the workflow supports the deployment.
  4. A database connection string and storage bucket URL can flow into the API’s environment variables when those outputs are exposed.
  5. The UI can show the resources as components on the Canvas when Canvas integration is enabled for the workflow.

Next steps

Biztraak infra deployments can build a dependency-aware foundation from the resources exposed by the selected workflow. Review the resulting resources, outputs, and logs before relying on them in a code deployment.