Skip to content

Add Schematic environment catalog integration#74

Merged
snowmead merged 2 commits into
mainfrom
feat/integration-schematic
Jul 16, 2026
Merged

Add Schematic environment catalog integration#74
snowmead merged 2 commits into
mainfrom
feat/integration-schematic

Conversation

@snowmead

@snowmead snowmead commented Jul 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • Phase 1 CatalogResource for schematic/schematic-environment (Wave 7).
  • Registry row + providers/schematic module, gap + hermetic provision tests.
  • Provisional OUTPUT_FIELDS (api_key) until mise run discover schematic/schematic-environment.
  • Branched from refresh tip 30df3de (plugin v0.25.0 fixtures). No smoke fixture.

Test plan

  • cargo nextest run -p stackless-integrations -E 'test(schematic)'
  • registry uniqueness + catalog_outputs_match_output_fields
  • mise run check (pre-push hook)

Note

Low Risk
Additive catalog provider registration with tests only; no changes to auth, existing providers, or runtime provisioning paths beyond the new registry row.

Overview
Adds Schematic as a managed Stripe Projects integration for schematic/schematic-environment, so stacks can declare a Schematic integration and reference ${integrations.<name>.api_key} in service env.

The new SchematicEnvironment resource is wired into the provider registry and module tree like other Wave catalog providers: global-only config with optional environment_type and name, resource kind integration-schematic, and provisional api_key output mapping until mise run discover pins the envelope. validate_config is a no-op for now; catalog alignment and hermetic provision behavior are covered by unit tests (including catalog_outputs_match_output_fields).

Reviewed by Cursor Bugbot for commit 06a178c. Bugbot is set up for automated code reviews on this repo. Configure here.

Provisional OUTPUT_FIELDS until discover; Wave 7 fixed-base family PR.
@cursor
cursor Bot enabled auto-merge July 15, 2026 23:37
@snowmead
snowmead merged commit 7e6b675 into main Jul 16, 2026
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant