greentic-deployer-dev 1.1.27219989263

Greentic deployer runtime for plan construction and deployment-pack dispatch
Documentation
# wizard.qaspec.yaml — local-process deployer env-pack (C6).
#
# This QASpec is intentionally minimal. The local-process deployer runs
# everything in-process against the developer's machine; there is no
# cloud account, no cluster, no IAM, no remote credentials to collect.
# The only operator-tunable surface today is the port range the handler
# searches for an available port at probe time (defaults to 8080..=8090
# in code; tests override via `LocalProcessDeployerHandler::with_port_range`).
#
# Shipping a one-question spec lets the operator's wizard driver:
#   1. prove the C6 seam end-to-end against a real env-pack;
#   2. surface a knob the operator MAY override per env without code changes;
#   3. give downstream env-packs (AWS-ECS, K8s, …) a reference shape to
#      mirror.
#
# A second question would be over-specifying for v1; the listen address
# is sourced from `host_config.listen_addr` (a different layer) and the
# runtime stub C5 already handles it.
#
# C6 ↔ Phase D split applies (answers recorded on the binding, not yet
# honored by today's `LocalProcessCredentials::validate` probe). See the
# AWS-ECS YAML's "Trust-boundary disclosure" header for the full
# reference write-up. Local-process's risk surface here is tiny.

id: greentic.deployer.local-process.wizard
title: Local-process deployer
version: "0.1.0"
description: >-
  Configuration for the local-process deployer env-pack. Local-process
  runs workers as child processes on the operator host; the only
  environment-scoped knob today is the port range it searches for an
  available port at probe time. Phase C: answers are captured on the
  binding (`answers_ref`) but NOT yet honored by `credentials validate`
  — the C2 probe uses the in-code default. Phase D wires the captured
  answer into the probe.
questions:
  - id: port_range
    type: string
    title: Worker port range
    description: >-
      Inclusive port range the local-process deployer searches for an
      available port. Format `<start>..=<end>`. Leave blank to use the
      built-in default (`8080..=8090`).
    required: false
    default_value: "8080..=8090"
    constraint:
      pattern: '^[0-9]+\.\.=[0-9]+$'