Release: v3.0.0-beta1 #411
Merged
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.
Notable Changes
While we always seek to minimize breaking changes, there is a substantial delta between Cloud Functions v1 and Cloud Functions v2, such that the GitHub Action was mostly rewritten.
"v3" supports 2nd generation Cloud Functions (
GEN_2). 1st generation Cloud Functions may work, butGEN_1is not supported. Usegoogle-github-actions/deploy-cloud-functions@v2for 1st generation functions."files" inputs such as
environment_variables_filehave been removed. To source values from a file, read the file in a prior step and set an output. There are many community-sponsored GitHub Actions that provide this functionality."memory" is now specified as a string with a suffix (e.g. "5Mb") instead of assuming megabytes.
"secret_env_vars" and "secret_volumes" have been combined into a single "secrets" input which accepts environment variable keys or filepaths.
Various fields were renamed to match the "v2" API, such as "service_account" and "min/max_instance_count".
Labels, environment variables, and secrets are still declarative, but they are not modified if no values are given. You can explicitly empty the value by setting the input to the literal string "{}".
Functions are only served over HTTPS (no HTTP). This is a requirement for Cloud Functions v2.
Since Cloud Functions v2 uses EventArc, you may need to enable the EventArc API and re-configure triggers (many inputs have changed to match the new API specification).
In accordance with our support policy, when "v3" is released as GA, we will stop supporting "v1" and continue to support "v2" and "v3".