chore(functions): migrate to 2nd for CI/CD and change docs link #801
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Official PR migrating the CI/CD process for the Igbo API in production to deploy to Google 2nd generation Cloud Functions.
Issue ticket number and link
N/A
Motivation and Context
We want to enable our continuous deployment pipeline for the 2nd gen Google Cloud Functions.
How Has This Been Tested?
Multiple versions of the Igbo API have been deployed directly from my computer. We monitored the 2nd for the past week to identify any regressions. We had a smooth week, so we are confident we can delete our old Cloud Function and continuously deploy it to our new function.
Screenshots (if appropriate):
N/A