Allow plugin containers to propagate env vars#168
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Greptile SummaryThis PR adds environment-variable propagation for plugin containers. The main changes are:
Confidence Score: 5/5This looks safe to merge. Managed containers are recreated with current environment values. Typed YAML scalar values are converted without dropping the plugin entry. No blocking issues found in the changed code.
What T-Rex did
Important Files Changed
Reviews (2): Last reviewed commit: "add e2e test" | Re-trigger Greptile |
In yaml config you can define env vars that will be exposed to the plugin container