Add KSA support to the indexing bot#3
Merged
Conversation
Maximilian-Nesslauer
added
enhancement
- MOD_ROOTS entry 'ksa': 'mods' and netkan-ksa.json status export - prod-stack.py: KSA remotes/repos/status key, InboundKsa.fifo, InflatorKsa service - Dev stack and compose files: KSA dev queue and inflator service - Tests mirrored for the third game; harness ia_collections fixed to a tuple Mirrors KSP2 (KSP-CKAN#284, KSP-CKAN#289); the game-id-driven services need no code changes.
Maximilian-Nesslauer
force-pushed
the
ksa-game-support
branch
from
July 4, 2026 17:49
45017cb to
471f67a
Compare
This was referenced Jul 4, 2026
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
1 participant
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 KSA as a third game to the NetKAN bot, mirroring how KSP2 was added (KSP-CKAN#284, generalized in KSP-CKAN#289):
Game.MOD_ROOTSentry'ksa': 'mods'(the client's KSA mod root) andnetkan-ksa.jsonin the status export.prod-stack.py: KSA netkan/ckanmeta remotes and repos, status key,InboundKsa.fifoqueue (outputs + SQS policies +INFLATION_QUEUES), and anInflatorKsaservice (GAME: KSA) incl. builder-service coverage.dev-stack.pyand both docker-compose files:InboundDevKsa.fifodev queue,inflator-ksadev service, KSA inflation/status env entries.ia_collectionsvalue is now a real tuple like its siblings.The scheduler, auto-freezer, download counter, and webhooks iterate the configured game ids since KSP-CKAN#289, so they need no code changes.
Notes / sequencing
kspckan/inflatorimage built from upstream KSP-CKAN/CKAN, which rejectsGAME=KSAuntil the client support lands there; the actual AWS deploy is the CKAN team's. Implement and verify here, upstream PR after the client merges (see Add KSA support to the indexing bot #1).CKANMETA_USER/NETKAN_USERstay the globalKSP-CKAN, so PR-opening paths (indexer staging, spacedock-adder, auto-freezer) would target a nonexistentKSP-CKAN/KSA-*repo. Resolution is a deploy-time decision: transfer the repos to KSP-CKAN (only the remote URLs flip), or extendGitHubPRto accept an owner-qualified repos value. Flagged for the upstream PR body.Testing
mypy netkanclean; pylint 10/10 on the changed source files.InflatorKsa,InboundKsa.fifo, remotes/repos/status keys); both compose files parse.Closes #1.