Skip to content

flow config init should emit a complete deploy.yaml from a bundle #429

Description

@abrichr

This is a product gap, not a copy gap. It was documented in the README copy pass / PR #428 ("docs: clarify governed and multi-app workflow paths", Codex thread "Update README copy surfaces") and left unimplemented.

The README now points operators at a governed path that assumes a complete deploy.yaml already exists:

openadapt-flow certify bundle --config deploy.yaml
openadapt-flow run bundle --profile standard --config deploy.yaml

There is no command that produces that file from a compiled bundle. Removing governed commands from the README is not the solution.

Proposed command

openadapt flow config init bundle --out deploy.yaml

Requirements

  • Bind the exact bundle digest and execution backend.
  • Generate the required policy, identity, effect, idempotency, and runtime sections.
  • Use secret references only; never copy live secrets into the emitted YAML.
  • Mark unresolved fields so they cannot be mistaken for completed contracts.
  • Fail certification until those required fields are complete.
  • Emit deterministic, schema-valid output.
  • Cover browser, native, RDP, and Citrix with tests.

Documented path after this lands

  1. openadapt flow config init bundle --out deploy.yaml
  2. Review and complete the YAML (resolve marked fields, bind secret references).
  3. openadapt-flow certify bundle --config deploy.yaml
  4. openadapt-flow run bundle --profile standard --config deploy.yaml

Do not treat removal of governed commands from the README as the solution.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions