pulumi-gcp-kotlin/com.pulumi.gcp.logging.kotlin/ProjectSinkArgs

ProjectSinkArgs

data class ProjectSinkArgs(val bigqueryOptions: Output<ProjectSinkBigqueryOptionsArgs>? = null, val customWriterIdentity: Output<String>? = null, val description: Output<String>? = null, val destination: Output<String>? = null, val disabled: Output<Boolean>? = null, val exclusions: Output<List<ProjectSinkExclusionArgs>>? = null, val filter: Output<String>? = null, val name: Output<String>? = null, val project: Output<String>? = null, val uniqueWriterIdentity: Output<Boolean>? = null) : ConvertibleToJava<ProjectSinkArgs>

Import

Project-level logging sinks can be imported using their URI, e.g. * projects/{{project_id}}/sinks/{{name}} In Terraform v1.5.0 and later, use an import block to import project-level logging sinks using one of the formats above. For exampletf import { id = "projects/{{project_id}}/sinks/{{name}}" to = google_logging_project_sink.default }

$ pulumi import gcp:logging/projectSink:ProjectSink When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), project-level logging sinks can be imported using one of the formats above. For example

$ pulumi import gcp:logging/projectSink:ProjectSink default projects/{{project_id}}/sinks/{{name}}

Constructors

ProjectSinkArgs

fun ProjectSinkArgs(bigqueryOptions: Output<ProjectSinkBigqueryOptionsArgs>? = null, customWriterIdentity: Output<String>? = null, description: Output<String>? = null, destination: Output<String>? = null, disabled: Output<Boolean>? = null, exclusions: Output<List<ProjectSinkExclusionArgs>>? = null, filter: Output<String>? = null, name: Output<String>? = null, project: Output<String>? = null, uniqueWriterIdentity: Output<Boolean>? = null)

Functions

toJava

open override fun toJava(): ProjectSinkArgs

Properties

bigqueryOptions

val bigqueryOptions: Output<ProjectSinkBigqueryOptionsArgs>? = null

Options that affect sinks exporting data to BigQuery. Structure documented below.

customWriterIdentity

val customWriterIdentity: Output<String>? = null

A user managed service account that will be used to write the log entries. The format must be serviceAccount:some@email. This field can only be specified if you are routing logs to a destination outside this sink's project. If not specified, a Logging service account will automatically be generated.

description

val description: Output<String>? = null

A description of this sink. The maximum length of the description is 8000 characters.

destination

val destination: Output<String>? = null

The destination of the sink (or, in other words, where logs are written to). Can be a Cloud Storage bucket, a PubSub topic, a BigQuery dataset or a Cloud Logging bucket . Examples:

disabled

val disabled: Output<Boolean>? = null

If set to True, then this sink is disabled and it does not export any log entries.

exclusions

val exclusions: Output<List<ProjectSinkExclusionArgs>>? = null

Log entries that match any of the exclusion filters will not be exported. If a log entry is matched by both filter and one of exclusions.filter, it will not be exported. Can be repeated multiple times for multiple exclusions. Structure is documented below.

filter

val filter: Output<String>? = null

The filter to apply when exporting logs. Only log entries that match the filter are exported. See Advanced Log Filters for information on how to write a filter.

name

val name: Output<String>? = null

The name of the logging sink. Logging automatically creates two sinks: _Required and _Default.

project

val project: Output<String>? = null

The ID of the project to create the sink in. If omitted, the project associated with the provider is used.

uniqueWriterIdentity

val uniqueWriterIdentity: Output<Boolean>? = null

Whether or not to create a unique identity associated with this sink. If false, then the writer_identity used is serviceAccount:cloud-logs@system.gserviceaccount.com. If true (the default), then a unique service account is created and used for this sink. If you wish to publish logs across projects or utilize bigquery_options, you must set unique_writer_identity to true.