github-mirrors/netris-nestri
1
0
Fork 0
mirror of https://github.com/nestriness/nestri.git synced 2026-09-19 09:15:19 +03:00
Code Issues Packages Projects Releases Wiki Activity

ci: restart the issuer before the API

Browse Source 
Units come back in the order their artefacts appear in the manifest, and the
API reaches the issuer over AUTH_INTERNAL_URL -- so api-then-auth means the
API spends a moment talking to a service that is restarting.
This commit is contained in:
Wanjohi
2026-09-17 01:44:50 +03:00
parent 4668c98785
commit 7859c8e13a
1 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
.github/workflows/release-prod.yml vendored
View File

@@ -190,6 +190,10 @@ jobs:
# the checksum of every artefact, so the agent can verify what it
# downloaded before it swaps anything into place.
#
# The order matters: units are restarted in the order they appear
# here, and the API's AUTH_INTERNAL_URL names the issuer, so the
# issuer comes back first.
#
# `unit` is what gets restarted. `nestri-migrate` has none on purpose
# — it is run, not served — and `migrate: true` is what makes the
# deploy run it *before* the swap. That ordering is why migrations
@@ -205,16 +209,16 @@ jobs:
"run": "${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}",
"migrate": true,
"artefacts": [
{
"name": "nestri-api",
"unit": "nestri-api",
"sha256": "$(sha256sum nestri-api | cut -d' ' -f1)"
},
{
"name": "nestri-auth",
"unit": "nestri-auth",
"sha256": "$(sha256sum nestri-auth | cut -d' ' -f1)"
},
{
"name": "nestri-api",
"unit": "nestri-api",
"sha256": "$(sha256sum nestri-api | cut -d' ' -f1)"
},
{
"name": "nestri-migrate",
"sha256": "$(sha256sum nestri-migrate | cut -d' ' -f1)"