Support for environment variables
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- javascript
调研方向
No files or tests are named. Start by tracing how the UI5 CLI reads YAML configuration and passes middleware and task configuration, then determine where environment-variable and dotenv resolution belongs; done means placeholders are resolved before middleware or task execution with dotenv supported out of the box.
由索引模型根据 Issue 内容生成。
描述
Is your feature request related to a problem? Please describe.
I would like to have an out of the box supported standard approach to use environment variables to configure my middlewares and tasks.
Why? As one of the maintainers of the middleware in the open-ux-tools, I have noticed a repetitive pattern: usage of environment variables. In nearly all our middlewares/tasks we support some kind of usage of environment variables as input. A quick search through other middlewares also shows that we are not the only ones but many others also have their way of allowing to provide parts of the configuration as env variables.
The problem is that everybody does their own thing leading to inconsistencies of how to use env variables.
Describe the solution you'd like
I'd prefer a very simple solution allowing me to define environment variable placeholders in my yaml e.g.
server:
customMiddleware:
- name: preview-middleware
afterMiddleware: compression
configuration:
debug: ${DEBUG}
The UI5 CLI should resolve the environment variable before calling my middleware so that the middleware implementation does not have to bother.
Please also support dotenv out of the box as part of the same feature.
Describe alternatives you've considered
No.
Additional context
No.
- 主要语言
- JavaScript
- 星标
- 509
- 派生
- 82
- 平均合并
- 1 天 5 小时
- 30 天内合并 PR
- 50
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
UI5/cli 的其他 Issue
-
Build cache: buildThemes cache is invalidated by irrelevant library.js / .library content changes未关闭module/ui5-builder module/ui5-fs module/ui5-project
难度 3/5 1-2 天 新手友好度 76/100
维护者通常 1 天内回复
-
module/ui5-project
难度 4/5 3-5 天 新手友好度 64/100
维护者通常 1 天内回复
-
[ROADMAP] UI5 CLI 6.0 / Specification Version 6.0可能重新可做 @flovogt 于 69 天前认领，目前没有进行中的 PR。 未关闭roadmap
UI5/cli#1485 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
build excludes from application project are not applied to dependencies可能重新可做 @flovogt 于 43 天前认领，目前没有进行中的 PR。 未关闭
UI5/cli#1446 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Option to specify custom UI5 config for workspace dependency resolution可能已有人在做 @flovogt 于 169 天前认领。 未关闭
UI5/cli#1369 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
相似的 Issue
-
good first issue
难度 1/5 1 小时以内 新手友好度 88/100
saayam-for-all/webapp#1919 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
Uuriko/project-room#3728 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 62/100
devops-thiago/ThrillhouseBot#1132 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 74/100
andromarces/agent-loops#886 ·
维护者通常 1 天内回复
-
bug effort:low model:light plan planner:gpt-6-1-sol tests
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复