How vouchedfor/consentbundle works
ConsentBundle is a Symfony bundle for recording email consent in AWS DynamoDB. An application configures the table name and encryption password, obtains the consent handler, encrypts an email, then calls the handler to retrieve or update consent choices; updates are persisted to DynamoDB. Internally, the extension processes configuration and loads the bundle’s service definitions. The excerpts show handler reads and writes, but do not expose the service-definition wiring, so that connection is omitted.
Main entry points: ConsentHandler.php Consent handler · VouchedForConsentExtension.php Config extension · Configuration.php Config schema · VouchedForConsentBundle.php Bundle registration
Components 7
Symfony Integration
- Bundle registration
VouchedForConsentBundle.php - Config schema
DependencyInjection/Configuration.php - Config extension
DependencyInjection/VouchedForConsentExtension.php - Service definitions
Resources/config/services.yml
Consent Handling
- Consent handler
Services/ConsentHandler.php
Persistence
- AWS DynamoDB
Other components
- Symfony application
Connections 7
- Symfony application → Bundle registration: registers
README.md - Symfony application → Config schema: configures
README.md - Config extension → Config schema: processes
DependencyInjection/VouchedForConsentExtension.php - Config extension → Service definitions: loads
DependencyInjection/VouchedForConsentExtension.php - Symfony application → Consent handler: calls
README.md - Consent handler → AWS DynamoDB: reads
Services/ConsentHandler.php - Consent handler → AWS DynamoDB: writes
Services/ConsentHandler.php