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.

Sign up for GitHub

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

Jump to bottom

Transition to running on AWS Lambda #41

Open
nathan-weinberg opened this issue Dec 6, 2023 · 1 comment · May be fixed by #51
Open

Transition to running on AWS Lambda #41

nathan-weinberg opened this issue Dec 6, 2023 · 1 comment · May be fixed by #51
Assignees
@devinmatte @nathan-weinberg
Labels
ci/cd Affects or Updates CI/CD

Comments

@nathan-weinberg
Copy link
Member

Apparently, GitHub Actions scheduled runs are automatically disabled after 60 days of inactivity in a repo. As such, we want to transition the bot away from GitHub Actions to AWS Lambda where we won't face this restraint.
@nathan-weinberg nathan-weinberg added the ci/cd Affects or Updates CI/CD label Dec 6, 2023
@nathan-weinberg nathan-weinberg self-assigned this Dec 6, 2023
@devinmatte
Copy link
Member

The cron was disabled again a few weeks ago, migrating to lambda is a must

@devinmatte devinmatte self-assigned this Jun 21, 2024
@devinmatte devinmatte linked a pull request Jun 21, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@devinmatte devinmatte

@nathan-weinberg nathan-weinberg

Labels
ci/cd Affects or Updates CI/CD
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migrating to Chalice Cron transitmatters/mbta-slow-zone-bot
2 participants
@devinmatte @nathan-weinberg