Skip to content

test(cli): enforce redaction across migrate and pull commands #450

Description

@scottescue

Outcome

End-to-end CLI tests prove that migrate, Pull, and Pull with Init never expose credentials, raw secret literals, unrestricted object names, or unsafe structured payloads.

In scope

  • CLI stdout, stderr, formatted errors, diagnostics, and exit paths.
  • Migrate, Pull, and Pull with Init success and failure scenarios.
  • Broad-scan, secret-literal, credential-resolution, cancellation, and cleanup failures.
  • Assertions against raw values and encoded/quoted variants.

Out of scope

  • Session-level redaction already covered by lower-level conformance tests.
  • Logging systems outside the built-in CLI boundary.

Acceptance criteria

  • Representative credential and secret values are absent from every captured output channel.
  • Broad-scan failures expose counts and safe categories without full object names.
  • Structured diagnostics and formatted errors enforce the same redaction contract.
  • Migrate, Pull, and Pull with Init retain actionable stable error codes after redaction.
  • Tests run deterministically with injected stores, sessions, and introspection fixtures.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:file-migrationsRC.1-style file-based migration workflowarea:pullIntrospection and source generation (grizzle pull)priority:highHigh: must ship within the current milestonetestingTests and test infrastructure

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions