-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
google_logging_project_sink supports destination log bucket #7590
google_logging_project_sink supports destination log bucket #7590
Comments
The We meant to update our documentation, but it looks like that fell through. @venkykuberan, can we update the docs stating that log bucket destinations are possible, and also add text stating that the user can set any destination they want? |
To clarify, the API expects the destination bucket to be in this form: Looks like we should also support passing in a bucket |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
Description
It seems there are only 3 possible destinations for terraform resource google_logging_project_sin:
https://www.terraform.io/docs/providers/google/r/logging_project_sink.html#destination
In fact, we can configure other 3 destinations. Please find GCP console screenshot below:
It would be nice to support destination cloud loggin bucket.
New or Affected Resource(s)
Potential Terraform Configuration
example
sink will look up logs byfilter
and send it to logging bucketdbalogs
(resource idlogging.googleapis.com/projects/my-project/locations/global/buckets/dbalogs
) in GCP projectmy-project
:References
https://cloud.google.com/logging/docs/export#sink-terms
https://www.terraform.io/docs/providers/google/r/logging_project_sink.html#destination
The text was updated successfully, but these errors were encountered: