shenlan/site-migration-toolkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(ci): update VAULT_ROLE to github-actions-site-migration-toolkit per user request

Browse Source
This commit is contained in:
Haitao Pan 2026-07-01 09:45:30 +08:00
parent 645cf0d669
commit c6b467b60a
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/deploy-env-migration.yaml vendored
View File

@ -63,7 +63,7 @@ concurrency:
env: env:
VAULT_ADDR: https://vault.svc.plus VAULT_ADDR: https://vault.svc.plus
VAULT_ROLE: github-actions-site-recovery VAULT_ROLE: github-actions-site-migration-toolkit
VAULT_KV: kv/data/CICD VAULT_KV: kv/data/CICD
VAULT_KV_OPENCLAW: kv/data/openclaw VAULT_KV_OPENCLAW: kv/data/openclaw
VPS_ROOT: infra/iac_modules/terraform-hcl-standard/vultr-vps VPS_ROOT: infra/iac_modules/terraform-hcl-standard/vultr-vps

8
README.md
View File

@ -53,8 +53,8 @@ Only reserve roadmap placeholders for:
### ⚠️ CI/CD Prerequisites (Important Notice) ### ⚠️ CI/CD Prerequisites (Important Notice)
If you are running the GitHub Actions workflow (`deploy-env-migration.yaml`), please ensure that your Vault environment is correctly configured: If you are running the GitHub Actions workflow (`deploy-env-migration.yaml`), please ensure that your Vault environment is correctly configured:
- **Vault Role**: The current configured role is `github-actions-site-recovery` (kept for backward compatibility with the old repository name). Ensure this role exists in your Vault instance. - **Vault Role**: The required role name is `github-actions-site-migration-toolkit`.
- **Role Binding**: If the role is bound to the repository name, make sure the `bound_claims` match or are updated to reflect the new repository name if you ever recreate the role. - **Role Binding**: Ensure the JWT `bound_claims` match the new repository name (`repo:ai-workspace-infra/site-migration-toolkit:ref:refs/heads/main` or similar).
--- ---
@ -111,5 +111,5 @@ If you are running the GitHub Actions workflow (`deploy-env-migration.yaml`), pl
### ⚠️ CI/CD 前置条件 (重要提示) ### ⚠️ CI/CD 前置条件 (重要提示)
如果您正在运行 GitHub Actions 流水线 (`deploy-env-migration.yaml`)，请确保您的 Vault 环境已正确配置： 如果您正在运行 GitHub Actions 流水线 (`deploy-env-migration.yaml`)，请确保您的 Vault 环境已正确配置：
- **Vault 角色 (Role)**: 当前配置的角色名为 `github-actions-site-recovery`（为兼容旧代码库名而保留）。请确保您的 Vault 实例中存在该角色。 - **Vault 角色 (Role)**: 所需的角色名为 `github-actions-site-migration-toolkit`。
- **角色绑定 (Role Binding)**: 如果该角色是基于代码库名称绑定的，请确保其 `bound_claims` 匹配，或者在重建角色时更新为新的代码库名称。 - **角色绑定 (Role Binding)**: 请确保 JWT 的 `bound_claims` 匹配新的代码库名称（例如 `repo:ai-workspace-infra/site-migration-toolkit:ref:refs/heads/main`）。