Skip to content

experiment: schema discovery [DO NOT MERGE] - #144

Draft
yesoreyeram wants to merge 22 commits into
mainfrom
schema-discovery
Draft

experiment: schema discovery [DO NOT MERGE]#144
yesoreyeram wants to merge 22 commits into
mainfrom
schema-discovery

Conversation

@yesoreyeram

Copy link
Copy Markdown
Collaborator

No description provided.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

TruffleHog Scan Results

Summary: Found 3 potential secrets (0 verified, 3 unverified)

  • Possible secret (PrivateKey) at registry/grafana-snowflake-datasource/schema.go:186----***---
  • Possible secret (PrivateKey) at registry/grafana-snowflake-datasource/settings.examples.gen.json:28----***---
  • Possible secret (PrivateKey) at registry/grafana-snowflake-datasource/schema.gen.json:173----***---

Review: Check if unverified secrets are false positives.


Ignoring False Positives:
To mark a false positive, add # trufflehog:ignore as an inline comment on the same line as the detected secret:

my_fake_secret = "AKIAIOSFODNN7EXAMPLE"  # trufflehog:ignore

This works for files that support line numbers (most source files). After adding the comment, push your changes and the scan will re-run.

Add the jsonData_httpHeaders field (indexedPair storage) plus a
"Custom HTTP Headers" group so the schema-driven config UI matches the
legacy @grafana/ui CustomHeadersSettings editor: header name ->
jsonData.httpHeaderName<N>, value -> secureJsonData.httpHeaderValue<N>.
Regenerate schema.gen.json / settings.gen.json.

Skip indexedPair fields in the conformance jsonData<->struct parity
checks (JSONDataMatchesStruct / JSONDataTypesMatchStruct): such fields
expand to dynamic indexed keys and have no single backing Go struct
field, mirroring how per-header httpHeaderValue<N> secrets are excluded
from SecureKeys.

Add registry/graphite/ui.parity.md documenting the parity validation
(Playwright capture of both UIs, conditional-field checks, and the
fileUpload evaluation).
@yesoreyeram
yesoreyeram force-pushed the schema-discovery branch 2 times, most recently from d9f5bb5 to 578b122 Compare July 14, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant