Joe Bowbeer

This may be possible using mongoose middleware, e.g., pre and post hooks. In theory, it should be possible by overriding $wrapCallback, but in my observation this is not capturing the...

Also see: https://github.com/googleapis/cloud-trace-nodejs/blob/master/src/plugins/plugin-mongoose.ts

If this tracing RFE moves forward, I suggest adding hooks for OpenTelemetry tracing, which is compatible with a number of different consumers, including XRay.

Updating prior art links for envoy-gateway https://gateway.envoyproxy.io/v1.0.1/tasks/security/ext-auth/ https://gateway.envoyproxy.io/v1.0.1/api/extension_types/#extauth

This looks like a reasonable approach. The same approach can be used for AWS SSM ParameterStore? Can this be applied to all secret store implementations that don't natively implement multiple...

On second look, it looks like this only supports a single level of string-valued keys. At least, I don't see tests for anything else. Note however that arbitrarily nested JSON...

Here's some test input from the docs: https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_secret_json_structure.html#reference_secret_json_structure_AD ```json { "awsSeamlessDomainDirectoryId": "d-12345abc6e", "awsSeamlessDomainUsername": "", "awsSeamlessDomainPassword": "", "directoryServiceSecretVersion": 1, "schemaVersion": "1.0", "keytabArns": [ "", "", "", ], "lastModifiedDateTime": "2021-07-19 17:06:58" }...

@passuied I think the AWS v2 auth package needs to be thought through before using AWS v2 auth in secretsmanager. Consider adding a separate package for AWS v2 auth. https://github.com/dapr/components-contrib/blob/main/common/authentication/aws2...

@passuied I suggest reverting v2 changes. When migrating to v2, all aws refs should be migrated. But at the moment, I see v2 code calling some aws functions. It's better...

@tillrohrmann what did you mean by "invoker's concurrency limit"?