-
-
Notifications
You must be signed in to change notification settings - Fork 14
SK-147 / add e2e test using simkube-ci-action #212
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #212 +/- ##
=======================================
Coverage 75.60% 75.60%
=======================================
Files 58 58
Lines 3291 3291
Branches 164 164
=======================================
Hits 2488 2488
Misses 697 697
Partials 106 106 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
drmorr0
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! :excited:
.github/workflows/simkube_e2e.yml
Outdated
| - name: Setup SimKube GitHub Action runner | ||
| uses: acrlabs/simkube-ci-action/actions/launch-runner@main | ||
| with: | ||
| ami-id: ami-03e5877b8398d4577 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit for the future: is it possible to reference the latest AMI from the parameter store, instead of hard-coding here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a todo, I think I want to make this the default behavior in the simkube-ci-action repo but allow overrides.
.github/workflows/simkube_e2e.yml
Outdated
| uses: acrlabs/simkube-ci-action/actions/launch-runner@main | ||
| with: | ||
| ami-id: ami-03e5877b8398d4577 | ||
| instance-type: c7a.xlarge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's maybe use an m6a.large here?
Related Links
Description and Rationale
How
launch-runneraction launches an ephemeral runner in the users AWS account (ACRL's AWS account in this case) that listens for jobs and runs one jobrun-simulationaction launches a simulation on an available custom SimKube runner using an available traceTest Steps
Other Notes
Our custom actions expose only a basic set of simulation parameters. In the future I expect to expose more functionality in the actions. The runner AMI is fully capable of running any SimKube simulation. If you can do it in SimKube you can do it on the runner!
[ ✅ ] I certify that this PR does not contain any code that has been generated with GitHub Copilot or any other AI-based code generation tool, in accordance with this project's policies.