From b2f2446b46bf02821d90ebedadae2bf7ae0e880e Mon Sep 17 00:00:00 2001
From: Taras Madan <tarasmadan@google.com>
Date: Mon, 5 Sep 2022 14:27:54 +0200
Subject: go.mod, vendor: update (#3358)

* go.mod, vendor: remove unnecessary dependencies

Commands:
1. go mod tidy
2. go mod vendor

* go.mod, vendor: update cloud.google.com/go

Commands:
1. go get -u cloud.google.com/go
2. go mod tidy
3. go mod vendor

* go.mod, vendor: update cloud.google.com/*

Commands:
1. go get -u cloud.google.com/storage cloud.google.com/logging
2. go mod tidy
3. go mod vendor

* go.mod, .golangci.yml, vendor: update *lint*

Commands:
1. go get -u golang.org/x/tools github.com/golangci/golangci-lint@v1.47.0
2. go mod tidy
3. go mod vendor
4. edit .golangci.yml to suppress new errors (resolved in the same PR later)

* all: fix lint errors

hash.go: copy() recommended by gosimple
parse.go: ent is never nil
verifier.go: signal.Notify() with unbuffered channel is bad. Have no idea why.

* .golangci.yml: adjust godot rules

check-all is deprecated, but still work
if you're hesitating too - I'll remove this commit
---
 vendor/cloud.google.com/go/logging/doc.go | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

(limited to 'vendor/cloud.google.com/go/logging/doc.go')

diff --git a/vendor/cloud.google.com/go/logging/doc.go b/vendor/cloud.google.com/go/logging/doc.go
index 3aa9b12b0..e3a9afdff 100644
--- a/vendor/cloud.google.com/go/logging/doc.go
+++ b/vendor/cloud.google.com/go/logging/doc.go
@@ -68,6 +68,21 @@ not recommended for normal use.
 	}
 
 
+Redirecting log ingestion
+
+For cases when runtime environment supports out-of-process log ingestion,
+like logging agent, you can opt-in to write log entries to io.Writer instead of
+ingesting them to Cloud Logging service. Usually, you will use os.Stdout or os.Stderr as
+writers because Google Cloud logging agents are configured to capture logs from standard output.
+The entries will be Jsonified and wrote as one line strings following the structured logging format.
+See https://cloud.google.com/logging/docs/structured-logging#special-payload-fields for the format description.
+To instruct Logger to redirect log entries add RedirectAsJSON() LoggerOption`s.
+
+
+	// Create a logger to print structured logs formatted as a single line Json to stdout
+	loggger := client.Logger("test-log", RedirectAsJSON(os.Stdout))
+
+
 Payloads
 
 An entry payload can be a string, as in the examples above. It can also be any value
@@ -84,6 +99,16 @@ If you have a []byte of JSON, wrap it in json.RawMessage:
 	j := []byte(`{"Name": "Bob", "Count": 3}`)
 	lg.Log(logging.Entry{Payload: json.RawMessage(j)})
 
+If you have proto.Message and want to send it as a protobuf payload, marshal it to anypb.Any:
+
+	// import
+    func logMessage (m proto.Message) {
+		var payload anypb.Any
+		err := anypb.MarshalFrom(&payload, m)
+		if err != nil {
+			lg.Log(logging.Entry{Payload: payload})
+		}
+	}
 
 The Standard Logger
 
-- 
cgit mrf-deployment