[ssh-wg] Build Python3 binary for salt-ssh
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- python
- 领域
- build-system, cli, devops, security
调研方向
Start by researching how to build static Python 3 binaries for x86_64 and ARM, including the libraries and pip binary required by salt-call. Review licensing and dependency-security requirements, then document a viable build, download or upgrade, and release approach; open a new SEP if the research requires major changes.
由索引模型根据 Issue 内容生成。
描述
Maintain and build a Python 3 binary that will be copied over with the tarball to be included in the salt-call run. This will also be gated by a config option that a user will need to enable if they always want to use the binary option.
How are we going to build the Python 3 binary?
We will build the binary statically for both x86_64 and ARM architecture. We will include the x86_64 binary by default in the Salt-SSH package. If the ARM architecture is detected we will include a warningto the user to download the binary. To make this download or upgrade of the binary easier, a switch/arg will be added to the salt-ssh cli tool that will handle this logic for both binaries. We will include the required libraries to run salt-call and include the pip binary. If users want to include other dependencies on top of this binary they can use the ssh_ext_alternatives feature to include the additional dependencies.
Python Binary Security Releases:
We will need to monitor and make sure our Python 3 binary and other built libraries are kept up to date with any security releases. Since the Python 3 binary will be managed outside of the salt repo we can do releases outside of the Salt release cycle to include these new patches and updates quickly. We will add a tool to help monitor if there are vulnerabiltiies in our dependencies. Either pyup or github security alerts
-
Research best way to build x86_64 python3 statically.
-
Need to review the licenses of all the libraries included in the build to see if there are any licensing conflict.
-
If there are any issues found during the research of this task which requires significant changes to the original plan might need to open a new SEP.
Part of work towards adding this SEP: saltstack/salt-enhancement-proposals#11
- 主要语言
- 没有语言数据
- 星标
- 36
- 派生
- 13
- 平均合并
- 2 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
saltstack/community 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 45/100
-
难度 1/5 1 小时以内 新手友好度 35/100
-
难度 2/5 1-3 小时 新手友好度 42/100
-
release process
难度 1/5 1 小时以内 新手友好度 30/100
-
release process
难度 5/5 一周以上 新手友好度 10/100
查看 saltstack/community 的全部 Issue
相似的 Issue
-
dependencies good first issue severity: low
难度 2/5 1-3 小时 新手友好度 85/100
TMHSDigital/GH-Arcade#27 ·
-
documentation good first issue
难度 1/5 1 小时以内 新手友好度 82/100
SO4-Markets/so4-oracle#1438 ·
维护者通常 1 天内回复
-
tech debt
难度 2/5 1-3 小时 新手友好度 83/100
AbsaOSS/living-doc-toolkit#116 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 3 天内回复
-
security
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复