* opentelemetry-sdk-extension-aws: make ec2 resource detector silent when loaded outside AWS
Assume that if we fail to get the token quickly we are not on AWS.
* opentelemetry-sdk-extension-aws: make ecs detector less chatty
Don't print warnings if we are not running inside an ecs instance so we can load the
resource detector more generally and avoid warnings in stderr.
* opentelemetry-sdk-extension-aws: make beanstalk detector less chatty
Don't print warnings if we are not running inside beanstalk so we can load the
resource detector more generally and avoid warnings in stderr.
* Add changelog
* opentelemetry-sdk-extension-aws: make eks detector less chatty
Don't print warnings if we are not running inside an eks instance so we can load the
resource detector more generally and avoid warnings in stderr.
* Update CHANGELOG
---------
Co-authored-by: Emídio Neto <9735060+emdneto@users.noreply.github.com>
* Point pylint to the root directories
Fixes#2657
* Use cd with instrumentations
* Do the same for the rest of the components
* Specify pylint configuration file
* Fix tox lint for sio-pika
* Fix commands for util-http and azure detector
* Fix lint for sdk-extension-aws
* Fix lint for opentelemetry-instrumentation
* Fix lint for grpc instrumentation
* Fix lint for opentelemetry-instrumentation
* Fix black an isort
* change bootstrap_gen to use a list instead of dict
* Bunch of updates
* Fix build
* fix lint
* Fix docs
* Fix lint
* More fixes
* Fix lint
* fix stupid mistake
---------
Co-authored-by: Christian Hartung <christian.hartung@olist.com>
* Make propagators conform to spec
* do not modify / set an invalid span in the passed context in case
a propagator did not manage to extract
* in case no context is passed to propagator.extract assume the root
context as default so that a new trace is started instead of continung
the current active trace in case extraction fails
* fix also ot-trace propagator which compared int with str trace/span ids
when checking for validity in extract
