Module resource 

Domain types for the four resources braze-sync manages.

See IMPLEMENTATION.md §6 for the complete type contracts. Adding a new variant to Resource / ResourceKind forces every match site in diff/, fs/, and braze/ to be updated — that compiler-enforced exhaustiveness is the central reason braze-sync is written in Rust (§2.4).

Re-exports

pub use catalog::Catalog;

pub use catalog::CatalogField;

pub use catalog::CatalogFieldType;

pub use content_block::ContentBlock;

pub use content_block::ContentBlockState;

pub use custom_attribute::CustomAttribute;

pub use custom_attribute::CustomAttributeRegistry;

pub use custom_attribute::CustomAttributeType;

pub use email_template::EmailTemplate;

pub use tag::Tag;

pub use tag::TagRegistry;

Modules

catalog

Catalog Schema domain types. See IMPLEMENTATION.md §6.2.

content_block

Content Block domain type. See IMPLEMENTATION.md §6.3.

custom_attribute

Custom Attributes are managed in registry mode.

email_template

Email Template domain type. See IMPLEMENTATION.md §6.4.

tag

Tags are managed in registry mode, derived from references on other resources.

Enums

Resource

Every resource type braze-sync manages, as a single sum type.

ResourceKind

Lightweight tag for filtering / CLI args. Mirrors Resource but without the payload.