Skip to content

Commit 7740f67

Browse files
feat(cloudfunctions): update the api
#### cloudfunctions:v2alpha The following keys were added: - schemas.SecretVersion (Total Keys: 4) - schemas.SecretVolume (Total Keys: 7) - schemas.ServiceConfig.properties.secretVolumes (Total Keys: 2) #### cloudfunctions:v2beta The following keys were added: - schemas.SecretVersion (Total Keys: 4) - schemas.SecretVolume (Total Keys: 7) - schemas.ServiceConfig.properties.secretVolumes (Total Keys: 2)
1 parent 7400fdb commit 7740f67

File tree

6 files changed

+204
-4
lines changed

6 files changed

+204
-4
lines changed

docs/dyn/cloudfunctions_v2alpha.projects.locations.functions.html

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -208,6 +208,19 @@ <h3>Method Details</h3>
208208
&quot;version&quot;: &quot;A String&quot;, # Version of the secret (version number or the string &#x27;latest&#x27;). It is recommended to use a numeric version for secret environment variables as any updates to the secret value is not reflected until new instances start.
209209
},
210210
],
211+
&quot;secretVolumes&quot;: [ # Secret volumes configuration.
212+
{ # Configuration for a secret volume. It has the information necessary to fetch the secret value from secret manager and make it available as files mounted at the requested paths within the application container.
213+
&quot;mountPath&quot;: &quot;A String&quot;, # The path within the container to mount the secret volume. For example, setting the mount_path as `/etc/secrets` would mount the secret value files under the `/etc/secrets` directory. This directory will also be completely shadowed and unavailable to mount any other secrets. Recommended mount path: /etc/secrets
214+
&quot;projectId&quot;: &quot;A String&quot;, # Project identifier (preferably project number but can also be the project ID) of the project that contains the secret. If not set, it is assumed that the secret is in the same project as the function.
215+
&quot;secret&quot;: &quot;A String&quot;, # Name of the secret in secret manager (not the full resource name).
216+
&quot;versions&quot;: [ # List of secret versions to mount for this secret. If empty, the `latest` version of the secret will be made available in a file named after the secret under the mount point.
217+
{ # Configuration for a single version.
218+
&quot;path&quot;: &quot;A String&quot;, # Relative path of the file under the mount path where the secret value for this version will be fetched and made available. For example, setting the mount_path as &#x27;/etc/secrets&#x27; and path as `secret_foo` would mount the secret value file at `/etc/secrets/secret_foo`.
219+
&quot;version&quot;: &quot;A String&quot;, # Version of the secret (version number or the string &#x27;latest&#x27;). It is preferable to use `latest` version with secret volumes as secret value changes are reflected immediately.
220+
},
221+
],
222+
},
223+
],
211224
&quot;service&quot;: &quot;A String&quot;, # Output only. Name of the service associated with a Function. The format of this field is `projects/{project}/locations/{region}/services/{service}`
212225
&quot;serviceAccountEmail&quot;: &quot;A String&quot;, # The email of the service&#x27;s service account. If empty, defaults to `{project_number}[email protected]`.
213226
&quot;timeoutSeconds&quot;: 42, # The function execution timeout. Execution is considered failed and can be terminated if the function is not completed at the end of the timeout period. Defaults to 60 seconds.
@@ -443,6 +456,19 @@ <h3>Method Details</h3>
443456
&quot;version&quot;: &quot;A String&quot;, # Version of the secret (version number or the string &#x27;latest&#x27;). It is recommended to use a numeric version for secret environment variables as any updates to the secret value is not reflected until new instances start.
444457
},
445458
],
459+
&quot;secretVolumes&quot;: [ # Secret volumes configuration.
460+
{ # Configuration for a secret volume. It has the information necessary to fetch the secret value from secret manager and make it available as files mounted at the requested paths within the application container.
461+
&quot;mountPath&quot;: &quot;A String&quot;, # The path within the container to mount the secret volume. For example, setting the mount_path as `/etc/secrets` would mount the secret value files under the `/etc/secrets` directory. This directory will also be completely shadowed and unavailable to mount any other secrets. Recommended mount path: /etc/secrets
462+
&quot;projectId&quot;: &quot;A String&quot;, # Project identifier (preferably project number but can also be the project ID) of the project that contains the secret. If not set, it is assumed that the secret is in the same project as the function.
463+
&quot;secret&quot;: &quot;A String&quot;, # Name of the secret in secret manager (not the full resource name).
464+
&quot;versions&quot;: [ # List of secret versions to mount for this secret. If empty, the `latest` version of the secret will be made available in a file named after the secret under the mount point.
465+
{ # Configuration for a single version.
466+
&quot;path&quot;: &quot;A String&quot;, # Relative path of the file under the mount path where the secret value for this version will be fetched and made available. For example, setting the mount_path as &#x27;/etc/secrets&#x27; and path as `secret_foo` would mount the secret value file at `/etc/secrets/secret_foo`.
467+
&quot;version&quot;: &quot;A String&quot;, # Version of the secret (version number or the string &#x27;latest&#x27;). It is preferable to use `latest` version with secret volumes as secret value changes are reflected immediately.
468+
},
469+
],
470+
},
471+
],
446472
&quot;service&quot;: &quot;A String&quot;, # Output only. Name of the service associated with a Function. The format of this field is `projects/{project}/locations/{region}/services/{service}`
447473
&quot;serviceAccountEmail&quot;: &quot;A String&quot;, # The email of the service&#x27;s service account. If empty, defaults to `{project_number}[email protected]`.
448474
&quot;timeoutSeconds&quot;: 42, # The function execution timeout. Execution is considered failed and can be terminated if the function is not completed at the end of the timeout period. Defaults to 60 seconds.
@@ -613,6 +639,19 @@ <h3>Method Details</h3>
613639
&quot;version&quot;: &quot;A String&quot;, # Version of the secret (version number or the string &#x27;latest&#x27;). It is recommended to use a numeric version for secret environment variables as any updates to the secret value is not reflected until new instances start.
614640
},
615641
],
642+
&quot;secretVolumes&quot;: [ # Secret volumes configuration.
643+
{ # Configuration for a secret volume. It has the information necessary to fetch the secret value from secret manager and make it available as files mounted at the requested paths within the application container.
644+
&quot;mountPath&quot;: &quot;A String&quot;, # The path within the container to mount the secret volume. For example, setting the mount_path as `/etc/secrets` would mount the secret value files under the `/etc/secrets` directory. This directory will also be completely shadowed and unavailable to mount any other secrets. Recommended mount path: /etc/secrets
645+
&quot;projectId&quot;: &quot;A String&quot;, # Project identifier (preferably project number but can also be the project ID) of the project that contains the secret. If not set, it is assumed that the secret is in the same project as the function.
646+
&quot;secret&quot;: &quot;A String&quot;, # Name of the secret in secret manager (not the full resource name).
647+
&quot;versions&quot;: [ # List of secret versions to mount for this secret. If empty, the `latest` version of the secret will be made available in a file named after the secret under the mount point.
648+
{ # Configuration for a single version.
649+
&quot;path&quot;: &quot;A String&quot;, # Relative path of the file under the mount path where the secret value for this version will be fetched and made available. For example, setting the mount_path as &#x27;/etc/secrets&#x27; and path as `secret_foo` would mount the secret value file at `/etc/secrets/secret_foo`.
650+
&quot;version&quot;: &quot;A String&quot;, # Version of the secret (version number or the string &#x27;latest&#x27;). It is preferable to use `latest` version with secret volumes as secret value changes are reflected immediately.
651+
},
652+
],
653+
},
654+
],
616655
&quot;service&quot;: &quot;A String&quot;, # Output only. Name of the service associated with a Function. The format of this field is `projects/{project}/locations/{region}/services/{service}`
617656
&quot;serviceAccountEmail&quot;: &quot;A String&quot;, # The email of the service&#x27;s service account. If empty, defaults to `{project_number}[email protected]`.
618657
&quot;timeoutSeconds&quot;: 42, # The function execution timeout. Execution is considered failed and can be terminated if the function is not completed at the end of the timeout period. Defaults to 60 seconds.
@@ -744,6 +783,19 @@ <h3>Method Details</h3>
744783
&quot;version&quot;: &quot;A String&quot;, # Version of the secret (version number or the string &#x27;latest&#x27;). It is recommended to use a numeric version for secret environment variables as any updates to the secret value is not reflected until new instances start.
745784
},
746785
],
786+
&quot;secretVolumes&quot;: [ # Secret volumes configuration.
787+
{ # Configuration for a secret volume. It has the information necessary to fetch the secret value from secret manager and make it available as files mounted at the requested paths within the application container.
788+
&quot;mountPath&quot;: &quot;A String&quot;, # The path within the container to mount the secret volume. For example, setting the mount_path as `/etc/secrets` would mount the secret value files under the `/etc/secrets` directory. This directory will also be completely shadowed and unavailable to mount any other secrets. Recommended mount path: /etc/secrets
789+
&quot;projectId&quot;: &quot;A String&quot;, # Project identifier (preferably project number but can also be the project ID) of the project that contains the secret. If not set, it is assumed that the secret is in the same project as the function.
790+
&quot;secret&quot;: &quot;A String&quot;, # Name of the secret in secret manager (not the full resource name).
791+
&quot;versions&quot;: [ # List of secret versions to mount for this secret. If empty, the `latest` version of the secret will be made available in a file named after the secret under the mount point.
792+
{ # Configuration for a single version.
793+
&quot;path&quot;: &quot;A String&quot;, # Relative path of the file under the mount path where the secret value for this version will be fetched and made available. For example, setting the mount_path as &#x27;/etc/secrets&#x27; and path as `secret_foo` would mount the secret value file at `/etc/secrets/secret_foo`.
794+
&quot;version&quot;: &quot;A String&quot;, # Version of the secret (version number or the string &#x27;latest&#x27;). It is preferable to use `latest` version with secret volumes as secret value changes are reflected immediately.
795+
},
796+
],
797+
},
798+
],
747799
&quot;service&quot;: &quot;A String&quot;, # Output only. Name of the service associated with a Function. The format of this field is `projects/{project}/locations/{region}/services/{service}`
748800
&quot;serviceAccountEmail&quot;: &quot;A String&quot;, # The email of the service&#x27;s service account. If empty, defaults to `{project_number}[email protected]`.
749801
&quot;timeoutSeconds&quot;: 42, # The function execution timeout. Execution is considered failed and can be terminated if the function is not completed at the end of the timeout period. Defaults to 60 seconds.

0 commit comments

Comments
 (0)