I12.7 · Watch New Relic
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go, javascript, openapi, python
调研方向
Start by reading the linked parent issue, the repository's CONTRIBUTING.md, and the provider page template; the issue does not name specific source files or tests. Verify New Relic's official sources and record when each was checked, then choose plugin formats and add catalog entries. Done means the provider page and docs/plugins.md are updated, saved-source and historical-change fixtures emit the expected events, and the client fix needed is documented.
由索引模型根据 Issue 内容生成。
描述
Part of https://github.com/patch-it-dev/patch-it-plugins/issues/15
Story
As a developer whose code calls New Relic, I want patch-it to know when New Relic breaks, deprecates or retires something, so I get the fix before production does.
Subtasks
- Find New Relic's sources and record them with the date checked (verify, don't guess; leave TBD if unknown):
- deprecations / sunset page
- API changelog (RSS / Atom if there is one)
- OpenAPI spec, if published
- official SDKs and their release notes / changelogs (Python and JS first)
- API versioning scheme (date-based, path, header, none)
- Pick the format plugin for each source (OpenAPI, RSS, GitHub Releases, changelog file, registry, prose) and add catalog lines
- Golden test: a saved copy of each source in, the expected events out
- One real historical breaking change as a replay fixture
- Provider page
providers/new-relic.mdfrom the template - Add or update its row in
docs/plugins.md(seeCONTRIBUTING.md) - Note what the client needs to fix it (existing handler, or a new fix kind in the client)
Acceptance criteria
- Daily ingest emits New Relic events, each with
source_urland an exactsource_excerpt - The replayed historical change produces the right events
- The provider page lists every source with its date checked
- 主要语言
- Go
- 星标
- 0
- 派生
- 0
- 平均合并
- 2 小时 59 分钟
- 30 天内合并 PR
- 17
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
patch-it-dev/patch-it-plugins 的其他 Issue
-
story
难度 2/5 1-3 小时 新手友好度 78/100
patch-it-dev/patch-it-plugins#120 ·
维护者通常 1 天内回复
-
story
难度 5/5 一周以上 新手友好度 35/100
patch-it-dev/patch-it-plugins#119 ·
维护者通常 1 天内回复
-
story
难度 4/5 3-5 天 新手友好度 35/100
patch-it-dev/patch-it-plugins#115 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue story
难度 5/5 一周以上 新手友好度 25/100
patch-it-dev/patch-it-plugins#104 ·
维护者通常 1 天内回复
-
good first issue story
难度 5/5 一周以上 新手友好度 35/100
patch-it-dev/patch-it-plugins#103 ·
维护者通常 1 天内回复
查看 patch-it-dev/patch-it-plugins 的全部 Issue
相似的 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 88/100
orion-belt-dev/orion-belt#181 ·
维护者通常 1 天内回复
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 79/100
kubesmarts/logic-operator#105 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 78/100
jakartaee/jakartablogs.ee#125 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
MUKE-coder/grit#228 ·
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100