2.5 KiB
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| Google: google_cloudfunctions_function | docs-google-datasource-cloudfunctions-function | Get information about a Google Cloud Function. |
google_cloudfunctions_function
Get information about a Google Cloud Function. For more information see the official documentation and API.
Example Usage
data "google_cloudfunctions_function" "my-function" {
name = "function"
}
Argument Reference
The following arguments are supported:
name- (Required) The name of a Cloud Function.
-
project- (Optional) The project in which the resource belongs. If it is not provided, the provider project is used. -
region- (Optional) The region in which the resource belongs. If it is not provided, the provider region is used.
Attributes Reference
In addition to the arguments listed above, the following computed attributes are exported:
name- The name of the Cloud Function.source_archive_bucket- The GCS bucket containing the zip archive which contains the function.source_archive_object- The source archive object (file) in archive bucket.description- Description of the function.available_memory_mb- Available memory (in MB) to the function.timeout- Function execution timeout (in seconds).runtime- The runtime in which the function is running.entry_point- Name of a JavaScript function that will be executed when the Google Cloud Function is triggered.trigger_http- If function is triggered by HTTP, this boolean is set.event_trigger- A source that fires events in response to a condition in another service. Structure is documented below.https_trigger_url- If function is triggered by HTTP, trigger URL is set here.labels- A map of labels applied to this function.
The event_trigger block contains:
-
event_type- The type of event being observed. For example:"providers/cloud.storage/eventTypes/object.change"and"providers/cloud.pubsub/eventTypes/topic.publish". See the documentation on calling Cloud Functions for a full reference. -
resource- The name of the resource whose events are being observed, for example,"myBucket" -
failure_policy- Policy for failed executions. Structure is documented below.
The failure_policy block supports:
retry- Whether the function should be retried on failure.