Repository navigation
chore: adopt strict-contracts (plugin.contracts.json + proto definitions) #9
Description
Part of workflow ecosystem strict-pb-typing migration. workflow-plugin-admin currently lacks a plugin.contracts.json declaring typed-proto contracts for its exposed module/step/trigger types.
Ask
- Add
plugin.contracts.jsonat repo root declaring each exposed type withmode: strict(orstrict_proto). - For each declared type, add corresponding proto message under
internal/contracts/(or similar). - Generate
*.pb.goand wire the typed server impl viasdk.ServeIaCPlugin/sdk.ServePluginFull/sdk.ServeHybridper the entrypoint pattern. - Update
plugin.jsonto bump minEngineVersion to v0.51.7+.
Reference precedents (just-merged)
- workflow-plugin-aws PR ci: add sync-plugin-version workflow #11 (v1.0.0 typed-IaC)
- workflow-plugin-azure PR chore: migrate to GoCodeAlone/modular #5 (v1.0.0)
- workflow-plugin-gcp PR ci: publish GoReleaser drafts after artifact upload #7 (v1.0.0)
- workflow-plugin-digitalocean v1.0.x (earlier strict-contracts cutover)
Filed as part of post-#617 autonomous workflow ecosystem strict-contracts audit. 🤖
Activity
intel352 commentedon May 14, 2026
Closing as no-surface: this plugin is a pure
ConfigProviderwith noModuleTypes(),StepTypes(), orTriggerTypes()implementations. It injects a config fragment that exercises engine-native module types (http.server, auth.*, storage.sqlite, etc.) but exposes zero plugin-owned types. Noplugin.contracts.jsonis needed — there are no types to declare contracts for. Theplugin.jsoncorrectly declares empty capabilities arrays.