Steve Coffman StevenACoffman

Get the content of the QR for Okta Verify app setup. It looks like this: oktaverify://email@domain.com/?t=XXXXX&f=YYYYY&s=https://DOMAIN.okta.com&issuer=DOMAIN.okta.com&isIdxEnabled=true
Replace XXXXX, YYYYY and DOMAIN to your values in curl below:

curl --request POST \
  --url https://DOMAIN.okta.com/idp/authenticators \
  --header 'Accept: application/json; charset=UTF-8' \
  --header 'Accept-Encoding: gzip, deflate' \
  --header 'Authorization: OTDT XXXXX' \
  --header 'Content-Type: application/json; charset=UTF-8' \

### Procedure:

Step 1: Go to https://console.cloud.google.com/alloydb/clusters?referrer=search&project=khan-academy Select Cluster, and Edit Read Pool
Step 2: Under Network Security, Select Require SSL (and optionally Enforce mTLS via AlloyDB connectors)
Step 3: Under Connectivity, Select Enable Public IP
Step 4: Unhide Advanced Configuration vieo, then Under Flags, click "Add database flag" and ensure at least these minimum flags are set to these values (other flags also may be set) | flag | value | |---|---|

Go struct Mapping options

Library	⭐	Technique
go-viper/mapstructure	8k	Technique
jinzhu/copier	6.1k	Reflection
thoas/go-funk	4.9k	Technique
darccio/mergo	3.1k	Technique
jmattheis/goverter	778	Codegen

How to Push to Someone Else's Pull Request

Let's say contributor has submitted a pull request to your (author) project (repo). They have made changes on their branch feature and have proposed to merge this into origin/master, where

origin -> https://github.com/author/repo.git

Now say you would like to make commits to their PR and push those changes. First, add their fork as a remote called

Simple DIY STS server Google Cloud Application Default Credential

or...how to use ADC and run your own STS token broker

An STS server will exchange one token for another. This protocol is used by GCP Workload Federation.

THis example runs your own STS server with GCP where the STS server accepts a source token, validates it and the returns a gcp access_token

For more information about STS servers, see

From https://www.reddit.com/r/golang/comments/1kwklgf/comment/mui4zkq/

Without a tool like buf, it's a lot of work for the consumers.

Let's say you leave the project layout exactly as in your question:

my-library/
└─ directory1/shared.proto

so downstream code can keep writing

https://thefridaydeploy.substack.com/p/less-is-more-with-opentelemetry-spans?r=36rml&triedRedirect=true

https://github.com/GoogleCloudPlatform/kubernetes-engine-samples/blob/main/observability/distributed-tracing/main.go

https://github.com/GoogleCloudPlatform/opentelemetry-demo/blob/main/kubernetes/opentelemetry-demo.yaml

https://github.com/mterhar/otel-go-batch ( https://www.honeycomb.io/blog/exotic-trace-shapes )

https://blog.bitdrift.io/post/observability-3-0

// ProtoDiff generates an indented summary of the diff between two protos'
// YAML representations. See ProtoToYAML for documentation on rewrites.
func ProtoDiff(a, b protoutil.Message, args DiffArgs, rewrites func(interface{})) string {
	toYAML := func(m protoutil.Message) string {
		if m == nil {
			return ""
		}
 str, err := ProtoToYAML(m, false /* emitDefaults */, rewrites)

	package main

	import (
	"google.golang.org/protobuf/proto"
	"google.golang.org/protobuf/reflect/protodesc"
	"google.golang.org/protobuf/reflect/protoreflect"
	"google.golang.org/protobuf/types/descriptorpb"
	"google.golang.org/protobuf/types/dynamicpb"
	)