Add support for DAPRSIDEKICK_XXX variables #14
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
It is now possible to define
DAPRSIDEKICK_XXX
variables to set or override top-level configuration options. Note that this feature is limited to those options defined in the DaprProcessOptions base class which will equalluy apply to either theSidecar
,Placement
orSentry
processes depending which is configured.For example you can now set
DAPRSIDEKICK_ENABLED=false
to completely disable Dapr Sidekick, which is useful if you are running inside a pod/container where Dapr is injected separately.Issue reference
Fixes Issue #9
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: