Configuring qBits

Component-specific configuration

A QBit defines its own config class and producer. There is no universal AuthCognitoConfig/QBitConfigInput settings API. Read the selected component's integration example and identify required backends, names, dependencies, and environment values.

The data template demonstrates ExampleDataQBitProducer.withConfig followed by produce(qInstance, "example-data"). The host must already contain the configured backend.

Naming and credentials

Use unique table, process, possible-value-source, and widget names. A table prefix alone does not make every component safe for multiple instances. Resolve credentials through the host's documented environment or secret-provider mechanism; do not assume arbitrary strings containing ${env.NAME} are automatically interpolated by every config field.

Validate

Run the component's checks, QInstanceValidator, and host integration tests. Verify missing configuration fails clearly and that allowed/denied operations behave correctly. See Creating QBits.