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
Treat _Default & _Required Sinks same as buckets (#9384) (#16513)
* Treat _Default & _Required Sinks same as buckets
* Update documentation.
* Update exclusions every time.
* Do not check if _Default bucket has been deleted.
* Clean-up log statements.
* Fixup documentation.
* Ensure SA IAM set before associating with bucket.
[upstream:407631823fe91540101b6747b98f75eafdc3ada4]
Signed-off-by: Modular Magician <[email protected]>
logging: `google_logging_project_sink` now will aqcuire and update the resource that already exists at the desired location. These buckets cannot be removed so deleting this resource will remove the bucket config from your terraform state but will leave the logging bucket unchanged.
Copy file name to clipboardExpand all lines: website/docs/r/logging_project_sink.html.markdown
+4-1
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,9 @@ Manages a project-level logging sink. For more information see:
18
18
19
19
~> **Note** You must [enable the Cloud Resource Manager API](https://console.cloud.google.com/apis/library/cloudresourcemanager.googleapis.com)
20
20
21
+
~> **Note:** The `_Default` and `_Required` logging sinks are automatically created for a given project and cannot be deleted. Creating a resource of this type will acquire and update the resource that already exists at the desired location. These sinks cannot be removed so deleting this resource will remove the sink config from your terraform state but will leave the logging sink unchanged. The sinks that are currently automatically created are "_Default" and "_Required".
0 commit comments