Crate stackless_integrations 

Integration provider routing and first-class adapters.

Substrates call into this crate for ProvisionIntegration steps. Stripe-backed provisioning delegates to stackless-stripe-projects.

Re-exports

pub use registry::known_outputs;

pub use registry::validate_all;

pub use stackless_provider_sdk;

Modules

config

error

hostable

Integration provider metadata consumed by the registry for validation, output checking, and lifecycle dispatch. Each catalog adapter (Clerk, …) implements Hostable once; the registry is built only from those impls.

observation

providers

registry

First-class integration provider registry: validation, outputs, dispatch.

resource

The generic catalog-resource integration: declare a config + output fields + a provider prefix, and get ProviderOps (provision/observe/destroy) for free.

Structs

ResourcePayload

The checkpoint payload for any catalog resource: the Stripe resource name (for observe/destroy) and the ${integrations.<name>.<output>} map.

Enums

IntegrationError

IntegrationObservation

What an integration resource looks like when re-checked beyond Stripe registration. Providers return empty drift until a check-time surface consumes it.

Traits

CatalogResource

A catalog resource: a typed config + the credential fields it exposes. The ProviderOps lifecycle is derived (blanket impl below), so a new resource is just this trait + a Hostable + one registry row.

ProviderOps

One integration provider’s lifecycle behaviour. The registry stores a &'static dyn ProviderOps per provider, so adding a provider is one registry row + this impl — dispatch never matches on provider strings.

Functions

destroy

finalize_stripe_instance

Delete the instance’s Stripe Projects environment after all resources are gone. Failures are ignored — the environment bills nothing.

is_integration_resource

observe

provision