renovatebot/renovate

Automatic util/http handling of dynamic credentials

Open

#11,325 建立於 2021年8月18日

在 GitHub 查看
 (1 留言) (19 反應) (0 負責人)TypeScript (14,066 star) (1,916 fork)batch import
help wantedpriority-3-medium

描述

What would you like Renovate to be able to do?

Support dynamic credentials such as for AWS CodeArtifact or ECR in a simpler and more generic manner.

If you have any ideas on how this should be implemented, please tell us here.

Instead of pushing credentials awareness up to the datasource layer, instead we could reuse the existing authType field to tell the http layer that a token or username/password is not your "regular" Bearer or Basic one. e.g. we could support authType=aws-ecr and authType=code-artifact. The datasource could be agnostic to it and the http layer is responsible for generating the "real" token to use in the auth headers, and maybe even caching it too.

Is this a feature you are interested in implementing yourself?

Yes

貢獻者指南

技術棧
typescriptnodejs
領域
backendtoolingdevopsinfrastructure
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Understanding of Renovate's HTTP layerKnowledge of authentication mechanismsFamiliarity with AWS CodeArtifact/ECR
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Examine the existing http layer in Renovate, likely in packages/manager/http.ts, to understand how authType is currently used. Investigate how datasources like AWS ECR handle credentials. Design a mechanism to allow the http layer to dynamically generate tokens based on authType values. Consider caching and token refresh logic. No linked PRs or comments yet, so start by analyzing the codebase and proposing an implementation approach.