Commit d494226
fix(dashboard): keep programmable stage list usable after PaaS publish (#3165)
Why this change was needed:
Publishing a programmable gateway from the developer center creates a
Release but no ProgrammableGatewayDeployHistory. The stage overview then
crashed when comparing deploy_history.version.
What changed:
- Treat a missing deploy history as not deploying from the gateway
- Keep empty deploy-history objects so serializers do not receive None
- Add a regression test for the PaaS-only publish path
Problem solved:
The environment overview no longer returns 500, so users can open the
page and publish from the gateway after a developer-center release.
Co-authored-by: Cursor <cursoragent@cursor.com>1 parent d3c3fdd commit d494226
2 files changed
Lines changed: 23 additions & 2 deletions
File tree
- src/dashboard/apigateway/apigateway
- biz/programmable
- tests/biz/programmable
Lines changed: 3 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
195 | 195 | | |
196 | 196 | | |
197 | 197 | | |
| 198 | + | |
198 | 199 | | |
199 | 200 | | |
200 | 201 | | |
| |||
204 | 205 | | |
205 | 206 | | |
206 | 207 | | |
207 | | - | |
| 208 | + | |
| 209 | + | |
208 | 210 | | |
209 | 211 | | |
210 | 212 | | |
| |||
Lines changed: 20 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
22 | 22 | | |
23 | 23 | | |
24 | 24 | | |
25 | | - | |
| 25 | + | |
| 26 | + | |
26 | 27 | | |
27 | 28 | | |
28 | 29 | | |
| |||
118 | 119 | | |
119 | 120 | | |
120 | 121 | | |
| 122 | + | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
0 commit comments