Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Suggested topic (maybe): Switching off dynamic updates

未关闭
#3,333 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
领域
documentation

调研方向

首先查看有关关闭动态更新的 KC 主题、生成的服务器配置参考,以及 issue 中链接的 updateTrigger 参考。与 Alasdair 确认其优先级以及与容器化应用的相关性。完成标准是:主题清楚地说明何时以及如何关闭动态更新,包含两个 XML 配置片段,并删除重复或不必要的部分。

由索引模型根据 Issue 内容生成。

描述

low priority

From reviewing the KC (check with Alasdair for prioritisation).

This topic in the KC:
https://www.ibm.com/support/knowledgecenter/SSAW57_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_setup_dyn_upd.html

It makes it seem far more complicated than it is and isn't really relevant to containerised apps (hence the low priority). It's also a badly structured topic (see Alasdair's comments below) that frames the need badly and then duplicates a load of the generated server config info for no real reason. When you take out all that, there's no much left of it. So then the important question is "Do users need to know how to turn off dynamic updates?" If so, that should be what the topic is answering (maybe with a useful config example).

Alasdair's comments as I noted them down when discussing the KC topic:

"Ops[Scenario 3]. Is this relevant to containerised apps? Mostly not because general advice would be to just redeploy docker containers. 90% of the time you probably don’t need dynamic config. however if you change a config map in kube and the configmap contains server config if you turn dynamic behaviour off you need to redeploy the docker containers
I kind of switch on whether that is a good thing or not. 12-factor would say don’t do it. Most people and 12-factor would suggest redeploying docker container. The KC topic includes how to stop doing dynamic updates because you don't need that if you're redeploying a container (also relevant in security hardening context). I wouldn't have the Notes box and instead link to the updateTrigger topic; also don't need the Procedure section because the preamble tells you all you need to know. The Restriction box should be removed. Just simplify this and say if you need to turn off dynamic updates (don't say "default settings"), this is how you'd do it, and show the two pieces of XML. (currently KC gives a lot of words for very little info - makes it feel complicated when it's not)."

主要语言
没有语言数据
星标
14
派生
58
平均合并
1 小时 4 分钟
30 天内合并 PR
21

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

OpenLiberty/docs 的其他 Issue

查看 OpenLiberty/docs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。