Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically Iterate Games + Add KSP2 Config #289

Merged
merged 4 commits into from
Apr 8, 2023

Conversation

techman83
Copy link
Member

@techman83 techman83 commented Mar 29, 2023

This PR is intended to come after #283 + #288 - will rebase when ready

Adds

  • games method that automatically returns a list of the configured games
  • KSP2 Configuration

Changes

  • Utilities configured within the stack will iterate through all available games (Scheduler/Freezer/Counter)

Fixes

  • Remove processed from the QueueHandler, avoiding the risk of the list growing perpetually until SQS throws an exception

Extra

  • Left the mirrorer out to focus on it as a separate piece in preparation for when we have > 50 mod versions

@techman83 techman83 force-pushed the refactor/utilities branch 2 times, most recently from afc4378 to fed152b Compare April 7, 2023 04:19
@techman83 techman83 marked this pull request as ready for review April 7, 2023 04:41
@techman83 techman83 requested a review from HebaruSan April 7, 2023 04:42
@techman83
Copy link
Member Author

@HebaruSan - this will still require rebasing of the git-repos work, but I have reabsed off master to make it a bit easier to review

@techman83 techman83 force-pushed the refactor/utilities branch from 828e113 to d550541 Compare April 8, 2023 04:00
Instead of needing to setup utilities to run per game, we can iterate through. There is
likely scope for this to be improved further, but this will bring ksp2 on reasonably
quickly.
This adds the relevant configuration for KSP2 indexing
It was unnesscary to add a class property for processed, this was a holdover from how the class
was previously written, and caused an issue as it essentially built up until trying to send
more than 10 for a delete to SQS, causing an exception. Now the list is a local variable and
the handler returns the entries as requried for the queue to delete them, avoiding the possibility
of it growing beyond the messages as set by MaxNumberOfMessages
ECS uses cloudwatch to schedule tasks, and needs to be able to pass through the IAM, to which
the scheduler needs permission to do that. Though the tasks are being renamed back, this prevents
a situation in the future where we add/change a task and wonder why it does not invoke and have
limited ability to diagnose beyond seeing it fail to invoke.
@techman83 techman83 force-pushed the refactor/utilities branch from 42ca905 to c000c6f Compare April 8, 2023 04:41
Copy link
Member

@HebaruSan HebaruSan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, looks fine. Let's see if it works! 🚀

@techman83 techman83 merged commit 473da42 into KSP-CKAN:master Apr 8, 2023
@techman83 techman83 deleted the refactor/utilities branch April 8, 2023 04:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants