Expand description
Provider-facing traits and helpers for stackless catalog integrations.
Implement Hostable + CatalogResource (or ProviderOps directly) and
register in stackless-integrations. Provisioning delegates to Stripe
Projects; this crate is the extension point for bespoke providers.
Re-exports§
pub use config::config_bool;pub use config::config_optional_string;pub use config::config_string;pub use error::IntegrationError;pub use hostable::BlockedSetting;pub use hostable::ConfigScope;pub use hostable::Hostable;pub use hostable::IntegrationHosting;pub use hostable::host_bound_hosts;pub use hostable::host_bound_supports;pub use observation::Drift;pub use observation::IntegrationObservation;pub use resource::CatalogResource;pub use resource::ResourcePayload;
Modules§
- config
- error
- hostable
- Integration provider metadata consumed by the registry for validation,
output checking, and lifecycle dispatch. Each catalog adapter (Clerk, …)
implements
Hostableonce; the registry is built only from those impls. - observation
- resource
- The generic catalog-resource integration: declare a config + output fields +
a provider prefix, and get
ProviderOps(provision/observe/destroy) for free.
Traits§
- Provider
Ops - One integration provider’s lifecycle behaviour. The registry stores a
&'static dyn ProviderOpsper provider, so adding a provider is one registry row + this impl — dispatch never matches on provider strings.