Skip to content

v0.5.3 — Plugin dependency resolution & unified AWS plugin

Choose a tag to compare

@alexconrey alexconrey released this 10 Aug 21:40
· 133 commits to main since this release
995fee2

What's new

Plugin dependency resolution

Plugins now declare capabilities via a metadata() WASM export. Deckwatch automatically topologically sorts them at load time — operators never need to worry about plugin ordering.

  • PluginMetadata with provides, depends_on, optional_depends_on capability IDs
  • Topological sort (Kahn's algorithm) before any apply() calls
  • Output threading: each plugin's PluginResult.outputs is passed to subsequent plugins as PluginContext.plugin_outputs

Cloud-agnostic plugin networking

  • allowed_hosts per plugin — controls which URLs the plugin can reach via extism's HTTP host function
  • config map per plugin — operator-supplied key-value pairs (credentials, endpoints) injected into extism config; deckwatch has zero cloud-specific knowledge

Plugin settings UI

Settings → Plugins now shows per-plugin allowed_hosts and config key-value editor (values containing "secret", "password", or "token" are auto-masked).

Also in this release

  • Ingress host chips are clickable links
  • service_account_name binding in PluginResult
  • Labels, annotations, and node affinity management in the deployment UI
  • update_deployment_labels, update_deployment_annotations, update_deployment_affinity MCP tools

Companion SDK

deckwatch-plugin-sdk v0.4.0 — PluginMetadata, plugin_outputs, outputs

AWS plugin

deckwatch-plugin-aws — unified IAM + RDS + S3 provisioning with AWS Backup snapshots, automatic dependency ordering