Skip to content

Issue 616 opa config validation#618

Closed
bdumpp wants to merge 5 commits into
masterfrom
issue-616-opa-config-validation
Closed

Issue 616 opa config validation#618
bdumpp wants to merge 5 commits into
masterfrom
issue-616-opa-config-validation

Conversation

@bdumpp

@bdumpp bdumpp commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

No description provided.

bdumpp and others added 4 commits July 7, 2026 13:32
Add shared typed OPA config structs, wire the new System and ProjectConfig fields through the config merge path, and validate unknown top-level keys during config loading and reconciliation.

Closes #616

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Restore customOPAConfig to *runtime.RawExtension so existing System
  resources with non-standard OPA keys are not rejected on read
- Remove ValidateRaw from v1beta1.OPAConfigSpec.UnmarshalJSON; move
  validation of spec.opa.config to the admission webhook (write-only)
- Fix nil pointer panic when legacy BundleServer or DecisionAPIConfig
  is absent (controller config without legacy OPA section)
- Fix ToMap to use encoding/json instead of gopkg.in/yaml.v2 so that
  json: struct tags and runtime.RawExtension values are handled correctly
- Fix scientific notation for large integers (UseNumber + int64 conversion)
- Always emit bundles.authz.resource in the base ConfigMap

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: bdumpp <mpp@bankdata.dk>
…OCP refactor

Signed-off-by: bdumpp <mpp@bankdata.dk>
@bdumpp bdumpp requested a review from a team as a code owner July 8, 2026 08:14
@bdumpp bdumpp closed this Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant