-
Notifications
You must be signed in to change notification settings - Fork 10
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
Remove AWS Lambda and GCP Cloudfunctions builds #140
Labels
cleanup
Maintenance, cleaning up codebase or repo
Milestone
Comments
TiganeteaRobert
added a commit
that referenced
this issue
Jun 10, 2022
TiganeteaRobert
added a commit
that referenced
this issue
Jun 14, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 1, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 1, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Aug 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the project was first created, builds for AWS lambda and cloudfunctions were created. We never use them and when we open source it just opens the door for people expecting us to support things we don’t want to support. Let’s just remove those builds and only support docker
The text was updated successfully, but these errors were encountered: