Configuration settings often depend on other settings or external resources to function correctly. Always implement validation to check these dependencies and provide clear error messages when requirements are not met.

When adding new configuration settings:

Identify all dependencies (other settings, external services, required credentials)
Implement validation that checks these dependencies are satisfied
Document interactions with other settings clearly
Use appropriate setting types (enums instead of free-form strings when possible)

Example validation pattern:

video_conversion_enabled:
  default: false
video_conversion_service:
  enum: "VideoConversionServiceSetting"
  default: "aws_mediaconvert"

With corresponding validation: “If video_conversion_enabled is true and video_conversion_service is aws_mediaconvert, then mediaconvert_role_arn and S3 credentials must be present.”

This prevents runtime failures and reduces user confusion by catching configuration errors early and providing actionable feedback.

Add Repository

Private Repository