Use aws api that accepts context as first parameter. Opentracing integration requires context as first parameter for propagation

[etsangsplk]

Opentracing relies on context that encap span metadata inside context to flow through in or out of process boundaries, components etc
I understand that that means breaking change, AWS SDK go offers a parallel set of API that incoporates ...WithContext. See below
https://github.com/aws/aws-sdk-go/blob/master/service/cloudformation/cloudformationiface/interface.go

Or you can carry context in the structure and add WithContext method, which is not quite golang idiom.

opentracing:

example
https://github.com/jaegertracing/jaeger/tree/master/examples/hotrod
https://github.com/jaegertracing/jaeger-client-go

[etsangsplk]

@harlow Any opinion about this suggestion?

[harlow]

hi @etsangsplk can you give a code example of where you'd like to pass the context? i'm fine w/ a breaking change if it makes the library easier to work with and encourages good metrics

[etsangsplk]

Found a way to hook into aws session,
#72

[etsangsplk]

Reopen until PR status is known

[harlow]

Hi @etsangsplk while overall I think #72 looks good. I've been trying to get my head around if we need all the open-tracing code scattered around the repo. Or if there is a way to have a Tracer interface that we can optionally pass in (like we do w/ Counter, Logging, Etc)