New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow passing multiple --resources-path
flags to daprd
#5909
Conversation
Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have not looked at the code yet, but I do miss E2E test for this. Is it possible with the current K8s centric approach? Is there a way to "manually" add the sidecar container in the test without relying on injector?
Because this only works in self-hosted mode, we cannot have E2E tests for this (same reason as every other time, sadly). It is also not meant to be run on K8s (that's what #5908 was for). Perhaps E2E tests could be created in the CLI repo when the CLI adds supports for this. |
We don't have E2E for self-hosted mode today, although technically it's possible add them by configuring a self-hosted sidecar on a Kubernetes deployment.
There are two separate issues here being mingled into one:
|
Albeit possible, this is not easy at all given our K8s test framework today. The test runner doesn't have code in place to deploy a daprd container (converting annotations into CLI flags etc), and some things would require large efforts such as being able to retrieve the TLS certificates to inject them into the Deployment. I agree with you both there's a need for self-hosted E2E tests, but I kindly ask that be considered outside of the scope of this PR given the large effort. In the meanwhile, I think this PR can be "E2E tested" in the Dapr CLI with relative ease. |
For sure, as we don't have an infrastructure for self-hosted E2E tests, I don't expect this PR to be any different than any other self-hosted PR in terms of expectations. |
Change requested is out of scope for this PR
Codecov Report
@@ Coverage Diff @@
## master #5909 +/- ##
==========================================
- Coverage 64.75% 64.62% -0.14%
==========================================
Files 165 165
Lines 17249 17274 +25
==========================================
- Hits 11170 11163 -7
- Misses 5214 5237 +23
- Partials 865 874 +9
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
…esources-path Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
This is a spin-off from #5908 which takes one of the two parts of the PR (the largest one) as described in #5585
It allows starting daprd with multiple
--resources-path
flags, to specify multiple folders to load resources (components, resiliency policies, declarative subscriptions) from.This allows, for example, maintaining components and resiliency policies in different folders, or maintain "shared" components in a separate folder from app-specific ones. More details can be found in #5585
It also includes some small tweaks and fixes encountered along the way.
TODO
--resources-path
flags indapr run
cli#1216--resources-path
flags in daprd and Dapr CLI docs#3151