[Bug] modules/access-context-manager, beyondcorp: evaluate all access level conditions and enforce endpoint verification
维护者通常 1 天内回复
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 68/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- gcp, terraform
调研方向
Start in modules/access-context-manager/main.tf: replace the direct conditions[0] indexing with a dynamic "conditions" block over each.value.basic.conditions, then make the unused project_id and region inputs optional in variables.tf. Next read modules/beyondcorp/main.tf and its variables.tf: adjust the encryption status list, bind the endpoint-verified access level to google_project_iam_member.iap_user, mark oauth_client_secret sensitive, and output .name. Done when both modules match the expected behavior and validation passes.
由索引模型根据 Issue 内容生成。
描述
Bug Description
modules/access-context-manager and modules/beyondcorp have functional and security gaps on main at commit db8271cf.
modules/access-context-manager/main.tfindexeseach.value.basic.conditions[0]directly instead of using adynamic "conditions"block overeach.value.basic.conditions, ignoring any additional conditions passed by callers, andvariables.tfrequires unusedproject_idandregioninputs.modules/beyondcorp/main.tfincludesENCRYPTION_UNSUPPORTEDinencryption_statuses, createsgoogle_access_context_manager_access_level.endpoint_verifiedwithout attaching it as an IAM condition ongoogle_project_iam_member.iap_user, leavesvar.iap_config.oauth_client_secretnon-sensitive invariables.tf, and returns the fullgoogle_access_context_manager_access_level.endpoint_verifiedresource object instead of.namein theendpoint_nameoutput.
Expected Behavior
modules/access-context-manageriterates over all elements ofeach.value.basic.conditionsand makes unused legacy variables optional.modules/beyondcorprequiresENCRYPTEDdevice status by default, binds theendpoint_verifiedaccess level condition togoogle_project_iam_member.iap_user, marksoauth_client_secretsensitive, and outputsgoogle_access_context_manager_access_level.endpoint_verified.name.
Additional Context
Tracked under #33. Split out from #348.
- 主要语言
- HCL
- 星标
- 61
- 派生
- 28
- 平均合并
- 1 天 22 小时
- 30 天内合并 PR
- 72
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
google/stellar-engine 的其他 Issue
-
[Documentation] 0-bootstrap: document Google producer organization ID inline for compute.restrictVpcPeering可能已有人在做 @Hariharan18092006 今天认领。 未关闭Documentation Level of Effort - Low Priority - Low Scope - Fast
难度 2/5 1-3 小时 新手友好度 73/100
google/stellar-engine#385 · 1 条评论 ·
维护者通常 1 天内回复
-
Enhancement Framework - FedRAMP High Level of Effort - Low Priority - Medium Scope - Blueprint Scope - Module
难度 2/5 1-3 小时 新手友好度 76/100
google/stellar-engine#320 ·
维护者通常 1 天内回复
-
[Feature Request] Gemini Enterprise CMEK index pre-warming, companion seed data store, declarative CmekConfig, and readiness probe可能已有人在做 @Calvin-Cheng1 于 2 天前认领。 未关闭Enhancement Gemini - Enterprise Gemini - Government Level of Effort - Medium Priority - High Scope - Blueprint Scope - Fast
google/stellar-engine#390 · 已指派 1 人 ·
维护者通常 1 天内回复
-
[Feature Request] Support regulated and non-regulated multi-tenancy within a single GCP Organization未关闭Enhancement
难度 5/5 一周以上 新手友好度 35/100
google/stellar-engine#388 ·
维护者通常 1 天内回复
-
Feature Request: Support regulated and non-regulated multi-tenancy within a single GCP Organization可能已有人在做 @Calvin-Cheng1 于 3 天前认领。 未关闭
google/stellar-engine#387 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 google/stellar-engine 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
librespeed/speedtest-rust#52 · 1 条评论 ·
-
[BUG] 1.2.3: init-worker-account.sh still sends email, so new deployments have no worker account未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug: ARCHITECTURE.md states three different workflow counts (88 / 69 / 69) and no test pins them未关闭area:docs area:workflow bug documentation priority:later
难度 2/5 1-3 小时 新手友好度 70/100
Ikalus1988/MisakaNet#4357 ·
维护者通常 1 天内回复
-
Recognise CloudFormation Guard (`cfn-guard`) as IaC security可能已有人在做 @costajohnt 今天认领。 未关闭enhancement good first issue
难度 2/5 1-3 小时 新手友好度 85/100
MustacheCase/zanadir#508 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
smswithoutborders/RelaySMS-Publisher#227 ·
维护者通常 1 天内回复