Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#197 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

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

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.

Description

enhancement

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.

Dominant language
HCL
Stars
51
Forks
21
Avg merge
1d 17h
Merged PRs (30d)
29

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/stellar-engine

All issues in google/stellar-engine

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.