更新RMDC系统的模块SKILL
This commit is contained in:
@@ -0,0 +1,32 @@
|
||||
# RMDC 模块依赖关系
|
||||
|
||||
## 依赖矩阵
|
||||
|
||||
| 模块 | 依赖模块 | 被依赖模块 |
|
||||
|:---|:---|:---|
|
||||
| rmdc-core | user-auth, jenkins-dac, exchange-hub, watchdog, project-mgmt, work-procedure, audit-log | - |
|
||||
| rmdc-user-auth | work-procedure, jenkins-dac, common | core |
|
||||
| rmdc-jenkins-branch-dac | audit-log, common | core, user-auth |
|
||||
| rmdc-exchange-hub | audit-log, common | core |
|
||||
| rmdc-watchdog | project-mgmt, common | core |
|
||||
| rmdc-project-management | audit-log, common | core, watchdog |
|
||||
| rmdc-work-procedure | audit-log, common | core, user-auth |
|
||||
| rmdc-audit-log | common | jenkins-dac, exchange-hub, project-mgmt, work-procedure |
|
||||
| rmdc-common | - | 所有模块 |
|
||||
|
||||
## 变更影响传播
|
||||
|
||||
```
|
||||
修改 rmdc-common → 需要重新测试所有模块
|
||||
修改 rmdc-user-auth JWT → 需要更新 rmdc-core 中间件
|
||||
修改 rmdc-audit-log 字段 → 需要更新所有写审计的模块
|
||||
```
|
||||
|
||||
## 发布顺序
|
||||
|
||||
1. rmdc-common (基础)
|
||||
2. rmdc-audit-log (审计基础)
|
||||
3. rmdc-work-procedure (工单基础)
|
||||
4. rmdc-jenkins-branch-dac / rmdc-project-management (并行)
|
||||
5. rmdc-user-auth / rmdc-exchange-hub / rmdc-watchdog (并行)
|
||||
6. rmdc-core (网关,最后)
|
||||
18
1-AgentSkills/developing-rmdc/reference/terminology.md
Normal file
18
1-AgentSkills/developing-rmdc/reference/terminology.md
Normal file
@@ -0,0 +1,18 @@
|
||||
# RMDC 术语表
|
||||
|
||||
| 术语 | 定义 |
|
||||
|:---|:---|
|
||||
| 一级授权 | 由 rmdc-project-management 管理的项目级权限 |
|
||||
| 二级授权 | 由 rmdc-watchdog 执行的 TOTP 动态授权 |
|
||||
| DAC | Discretionary Access Control,自主访问控制(Jenkins 分支权限) |
|
||||
| RBAC | Role-Based Access Control,基于角色的访问控制 |
|
||||
| JWT | JSON Web Token,用户认证令牌 |
|
||||
| 工单 | 需要审批的变更请求,由 rmdc-work-procedure 管理 |
|
||||
| 指令生命周期 | MQTT 指令从发送到完成的状态流转 |
|
||||
| SuperAdmin | 超级管理员,拥有系统全部权限 |
|
||||
| Admin | 管理员,可管理普通用户和三方用户 |
|
||||
| Normal | 普通用户 |
|
||||
| Third | 三方用户,最低权限 |
|
||||
| 谁注册谁管理 | 用户管理原则:注册人负责管理被注册用户的生命周期 |
|
||||
| RSA-OAEP | RSA 最优非对称加密填充,用于密码传输加密 |
|
||||
| bcrypt | 密码哈希算法,用于密码存储 |
|
||||
@@ -0,0 +1,36 @@
|
||||
# RMDC 版本兼容策略
|
||||
|
||||
## 版本号规范
|
||||
|
||||
采用语义化版本:`MAJOR.MINOR.PATCH`
|
||||
|
||||
- **MAJOR**: 不兼容的 API 变更
|
||||
- **MINOR**: 向后兼容的功能新增
|
||||
- **PATCH**: 向后兼容的问题修复
|
||||
|
||||
## 兼容性规则
|
||||
|
||||
### API 兼容
|
||||
- 新增可选字段:兼容
|
||||
- 新增必填字段:Breaking Change
|
||||
- 删除字段:Breaking Change
|
||||
- 修改字段类型:Breaking Change
|
||||
|
||||
### 数据库兼容
|
||||
- 新增可空列:兼容
|
||||
- 新增非空列(有默认值):兼容
|
||||
- 删除列:Breaking Change
|
||||
- 修改列类型:需评估
|
||||
|
||||
### MQTT 消息兼容
|
||||
- 新增可选字段:兼容
|
||||
- 消息必须包含版本字段
|
||||
- 消费者必须忽略未知字段
|
||||
|
||||
## Breaking Change 处理流程
|
||||
|
||||
1. 提前通知所有相关模块负责人
|
||||
2. 创建新版本接口(v2)
|
||||
3. 旧版本标记废弃(Deprecated)
|
||||
4. 设定过渡期(建议 2 个迭代)
|
||||
5. 过渡期结束后下线旧版本
|
||||
Reference in New Issue
Block a user