Idea: an offline-first switch (COGNIS_FEEDS_OFFLINE) for locked-down enclaves #12
cognis-digital
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Idea. The feed layer is built for air-gapped gear (fetch once, cache, re-serve offline), but the default posture is still online:
datafeeds.getrefreshes over HTTPS when the cache is older than 24h, and thefeeds.*helpers takeofflineper-call defaulting toFalse. So a freshfeeds enrich(without--offline) attempts an outbound fetch.On a genuinely locked-down enclave that's backwards: you'd rather the tool never touch the network unless explicitly told to, and an unexpected egress attempt can itself trip a monitor.
Proposal. Honor an env var —
COGNIS_FEEDS_OFFLINE=1— as a global default forofflineacrossdatafeeds.getand thefeeds.*enrichment helpers. Set it once in the enclave's environment and the whole tool is offline-first; the CLI--offlineflag stays as a per-invocation override, and unset behaviour is unchanged. Tracked as #9.Related question for operators: would you also want a hard mode that raises if anything tries to go online while the flag is set (fail-closed), vs. the softer "serve stale cache, never fetch"? Curious which matches your accreditation posture.
Beta Was this translation helpful? Give feedback.
All reactions