You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,6 +102,18 @@ steps:
102
102
- `build_environment_variables_file`: (Optional) Path to a local YAML file
103
103
containing variables. See 'env_vars_file' for syntax.
104
104
105
+
- `docker_repository`: (Optional) User managed repository created in Artifact
106
+
Registry optionally with a customer managed encryption key. If specified,
107
+
deployments will use Artifact Registry. If unspecified and the deployment is
108
+
eligible to use Artifact Registry, GCF will create and use a repository named
109
+
'gcf-artifacts'for every deployed region. This is the repository to which the
110
+
function docker image will be pushed after it is built by Cloud Build.
111
+
112
+
- `kms_key_name`: (Optional) Resource name of a Google Cloud KMS crypto key used
113
+
to encrypt/decrypt function resources. If specified, you must also provide an
114
+
artifact registry repository using the `docker_repository` field that was
115
+
created with the same key.
116
+
105
117
- `credentials`: (**Deprecated**) This input is deprecated. See [auth section](https://github.com/google-github-actions/deploy-cloud-functions#via-google-github-actionsauth) for more details.
106
118
Service account key to use for authentication. This should be
107
119
the JSON formatted private key which can be exported from the Cloud Console. The
0 commit comments