Commit 2f172ee
fix(workflow): Add SKIP_AUTH default value to prevent Pydantic validation errors
This PR fixes Pydantic validation errors that were occurring when the SKIP_AUTH secret was empty.
## Problem
When SKIP_AUTH secret is not set or empty, the backend receives an empty string '', causing:
```
Input should be a valid boolean, unable to interpret input
[type=bool_parsing, input_value='', input_type=str]
```
This was causing backend deployments to fail during the Code Engine application startup.
## Solution
Added default value 'false' to SKIP_AUTH environment variable:
**Before**:
```yaml
SKIP_AUTH: ${{ secrets.SKIP_AUTH }}
```
**After**:
```yaml
SKIP_AUTH: ${{ secrets.SKIP_AUTH || 'false' }}
```
Now when the secret is empty, the backend receives 'false' instead of '', which Pydantic can parse as a boolean.
## Testing
This fix will be validated in the next deployment workflow run. Expected behavior:
- If SKIP_AUTH secret is set: uses that value
- If SKIP_AUTH secret is empty/unset: defaults to 'false'
- Backend starts successfully without Pydantic validation errors
## Related
- Part of deployment fixes series (breaking down PR #641)
- Related to PR #642 (backend Docker fixes)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>1 parent 3e92d10 commit 2f172ee
1 file changed
+4
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
85 | 85 | | |
86 | 86 | | |
87 | 87 | | |
88 | | - | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
89 | 91 | | |
90 | 92 | | |
91 | 93 | | |
| |||
341 | 343 | | |
342 | 344 | | |
343 | 345 | | |
344 | | - | |
| 346 | + | |
345 | 347 | | |
346 | 348 | | |
347 | 349 | | |
| |||
0 commit comments