google / google/stellar-engine

[Feature Request]Customize Org Policy Enforcement Based on Regime Setting

Open
#197 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
HCL
Stars
49
Forks
20
Avg merge
3d 14h
Merged PRs (30d)
28

Description

## Feature Description and Use Case
Currently Stellar Engine has no option to customize org policy enforcement based on Regime setting. Org policies are static and stored under fast/stages-aw/0-bootstrap/data/org-policies/

This has led to issues where org policies will be enforced on regime entries that don't even support the api, for example, at IL5 oslogin.googleapis.com is not currently enabled, yet we still have an org policy set that mandates oslogin enforcement.

- [compute_policy.yaml#L84](https://github.com/google/stellar-engine/blob/f64ce6cd116fa6ecf5f96c8ba99fc44aafa3411e/fast/stages-aw/0-bootstrap/data/org-policies/compute_policy.yaml#L84)

Contributor guide

Open the contributing guide

Research direction

Start with fast/stages-aw/0-bootstrap/data/org-policies/compute_policy.yaml, especially line 84, and inspect the other files in that directory. Trace how the Regime setting is represented and how these static policies are applied; the issue does not name an entry point, tests, or a defined completion condition, so the desired conditional behavior needs clarification before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
gcp
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.