| name | post-build-validation |
| description | Validate side effects after build/deploy operations with graceful degradation |
| domain | error-handling, resilience, observability |
| confidence | low |
| source | earned |
Context
When build or deployment operations rely on external systems (APIs, remote commands, databases), individual operations can fail silently or be rate-limited. Post-build validation helps detect these failures and provides observability without blocking the entire process.
Patterns
Validate After Build, Not During:
- Separate validation logic from build logic
- Call validation methods after primary build operations complete
- Keeps build methods focused on construction, validation methods on verification
Graceful Degradation:
- Log warnings instead of throwing exceptions
- Return boolean success/failure instead of throwing
- Catch and handle exceptions in validation code to prevent cascading failures
- Use
LogWarning() with structured logging (include coordinates, expected values)
Verification Helper Pattern: