Bernd Verst
Bernd Verst
I think whenever an app uses the explicit Configuration CRD way to configure middlewares we should disregard the priority approach. The Configuration CRD is most explicit and therefore should always...
Conceivably a given component could be used in both pipelines at the same time. So maybe it should be: ```yaml - name: pipelineType value: appHttpPipeline,httpPipeline - name: priority value: 2...
Are you saying the component yaml file you used is **exactly** the one from the docs? ```yaml apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: sentinel spec: type: middleware.http.sentinel version: v1 metadata:...
Please note the component is alpha, so we do not provide patch releases for Dapr to address this. Hopefully someone has a chance to investigate this for the 1.14 release....
@bunengxiu right now nobody is working on or investigating this component. It might not be fixed until 1.14 or later (probably later).
@Jossec101 sounds good - can you comment here with `/assign` please? This of course cannot be released until Dapr 1.14
One complication factor: You also should cover the new functionality in our integration test (certification test) here: https://github.com/dapr/components-contrib/tree/main/tests/certification/pubsub/aws/snssqs Writing the test and verifying that everything works (e.g. calling the AWS...
No objections from me (though I do not specialize in AWS components). It sounds useful and implementing via the metadata makes sense. PRs welcome - but if PRs are added...
> Going to let this sit until closer to code freeze ~May 28th, as this should be part of the release process. If you don't want something merged you should...
Is this still being worked on?