Add the KSA inflator to deploy.yml and bounce.yml - #45
Merged
Maximilian-Nesslauer merged 1 commit intoJul 4, 2026
Merged
Conversation
- deploy.yml: include InflatorKsa in the upload-inflator redeploy loop - bounce.yml: add Ksa to the matrix
Maximilian-Nesslauer
added
enhancement
averageksp
approved these changes
Jul 4, 2026
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the KSA inflator to the two workflows that enumerate the per-game inflator services, mirroring how KSP2 appears in the same places:
deploy.yml:InflatorKsajoins the redeploy loop in theupload-inflatorjob.bounce.yml:Ksajoins thegamematrix (the job derives the service name asInflator${{ matrix.game }}).Deliberately nothing else: the diff stays a pure mirror of the existing KSP2 entries.
Sequencing
Both workflows are disabled in this fork (they need upstream's DockerHub/AWS secrets), so the change is inert here; the files ship with the eventual upstream PR. The
InflatorKsaECS service itself is created from NetKAN-Infra'sprod-stack.py(KSAModding/NetKAN-Infra#3) by the CKAN team's AWS deploy. Two notes to carry into the upstream PR body (#37):redeploy-service --service-name InflatorKsacall fails, but the deploy step still reports green because the loop backgrounds the calls and closes with a barewait(pre-existing pattern, unchanged here). So landing these entries before the service is provisioned does not break deploys.fail-fastthe sibling Ksp/Ksp2 jobs get cancelled. Left as-is to keep the diff minimal; worth mentioning upstream so a bounce is not dispatched between the client merge and the service provisioning.Verification
YAML parse of both files is clean, plus a semantic check that the matrix is
[Ksp, Ksp2, Ksa]. No runnable surface in this fork (both workflows disabled).Closes #36. Part of KSP-CKAN#4457.