* support tracestate can be propagated in PubSub
* add trace state
Co-authored-by: Long Dai <long.dai@intel.com>
Co-authored-by: Ian Luo <ian.luo@gmail.com>
Co-authored-by: Simon Leet <31784195+CodeMonkeyLeet@users.noreply.github.com>
Co-authored-by: Dapr Bot <56698301+dapr-bot@users.noreply.github.com>
Co-authored-by: Long Dai <long.dai@intel.com>
Co-authored-by: Artur Souza <artursouza.ms@outlook.com>
Co-authored-by: Dapr Bot <56698301+dapr-bot@users.noreply.github.com>
* Move Service Bus Pubsub/Binding to common auth
Both the pubsub and input/output binding for Azure Service Bus were
connecting via a connection string. This is still supported but will
now fallback to using AAD from the common auth library. This is also
the recommended auth pattern going forward.
* Move AMPQ specific auth and fix linter issues
* Make conn string and namespace mutually exclusive
* Move resourceName to a constant
* Update auth_amqp.go
* Update auth.go
Co-authored-by: Long Dai <long.dai@intel.com>
Co-authored-by: Simon Leet <31784195+CodeMonkeyLeet@users.noreply.github.com>
Co-authored-by: Artur Souza <artursouza.ms@outlook.com>
Co-authored-by: Dapr Bot <56698301+dapr-bot@users.noreply.github.com>
There is an internal race condition in MQTT client Publish method when
configured with autoreconnect (default) where the call can fail if the
connection is broken right after the outgoing event is queued but before
the dead connection is blocked.
This change mitigates that on the Dapr side with a limited retry loop
3 times at fixed 200ms interval as a patch before the Dapr resiliency
feature is introduced that exposes more generalized retry controls to
the dev.
Co-authored-by: Bernd Verst <4535280+berndverst@users.noreply.github.com>
Co-authored-by: Long Dai <long.dai@intel.com>
Co-authored-by: Artur Souza <artursouza.ms@outlook.com>
Co-authored-by: Dapr Bot <56698301+dapr-bot@users.noreply.github.com>
With the addition of the certification tests, changes in the go.mod
definition for component-contrib will also need to be propagated to the
go.mod for each of the tests under tests/certification.
- Add a `make modtidy-all` action to support updating all go.mod files.
- Update developing-component.md to include use of `make modtidy-all`.
Co-authored-by: Artur Souza <artursouza.ms@outlook.com>
Co-authored-by: Dapr Bot <56698301+dapr-bot@users.noreply.github.com>
* Authentication for new Azure SDK
* Updated keyvault to use new Azure SDK
* 🙈
* Update authentication/azure/auth.go
* Update authentication/azure/auth.go
* Update authentication/azure/auth.go
* Reintroduce changes from PR 1132 without updating ASB
* Lint 💄
* Marking contexts as TODO as they'll need a timeout
As per conversation with @berndverst
* Update certification tests with no auth libraries
Co-authored-by: Bernd Verst <4535280+berndverst@users.noreply.github.com>
* Fixing publish/subscribe race condition in RabbitMQ component.
Added amqpReady function to tests to wait for RabbitMQ readiness.
Tweaks to when subscribed is signaled in the test.
* Update go.mod(s)
The existing Skip Duplicate Actions pre-job will effectively ignore the
command `/ok-to-test` from repository_dispatch because the testing
triggered by a PR will usually be seen as transferrable, even though
the intention for `/ok-to-test` is to run a superset of tests triggered
by the PR.
To fix this, both the conformance and certification workflows will
always generate the test matrix if the trigger is a respository_dispatch
regardless of the test duplication check.
* Fix warning in smtp binding when user and password are set
* Remove nolint comment
Co-authored-by: Yaron Schneider <yaronsc@microsoft.com>
Co-authored-by: Artur Souza <artursouza.ms@outlook.com>
Co-authored-by: Dapr Bot <56698301+dapr-bot@users.noreply.github.com>
Laurence
Phil Kedy
Dmitry Shmulevich
Amit Mor
huazhongming
Simon Leet
xj524598
Taction
halspang
Tao Jiang
Artur Souza
Alessandro (Ale) Segala
Bernd Verst
yellow chicks
Sergey Krutsko
Long Dai
Hossam Kandil
Willem Meints