Skip to content

[Do not merge] Add initial Google Cloud Run code - still working through API-to-Engine comms.#145

Open
pcgeek86 wants to merge 1 commit intomainfrom
2026-03-google-cloud-run
Open

[Do not merge] Add initial Google Cloud Run code - still working through API-to-Engine comms.#145
pcgeek86 wants to merge 1 commit intomainfrom
2026-03-google-cloud-run

Conversation

@pcgeek86
Copy link
Contributor

Proposed changes

Types of changes

What types of changes does your code introduce to the Deepgram self-hosted resources?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update or tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING doc
  • I have tested my changes in my local self-hosted environment
    • Please describe your testing setup and methodology here
  • I have added necessary documentation (if appropriate)

Further comments

@pcgeek86 pcgeek86 requested review from a team and therealevanhenry as code owners March 17, 2026 21:36
@pcgeek86 pcgeek86 force-pushed the 2026-03-google-cloud-run branch from 93939f6 to a43372d Compare March 17, 2026 21:44
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.

1 participant