Skip to content

Show resource names, not config values, on /meta; front-end error log for maintainers only - #647

Merged
mahmoud merged 1 commit into
masterfrom
fix/meta-no-resource-values
Oct 10, 2026
Merged

mahmoud merged 1 commit into
masterfrom
fix/meta-no-resource-values

Conversation

@lgelauff

@lgelauff lgelauff commented Oct 4, 2026

Copy link
Copy Markdown
Collaborator

/meta and /meta/json/ are public. clastic's "Application Resources" section shows the first 70 characters of repr() of each app resource, so for config it showed the start of the config dict to anyone.

  • The resource section now lists each resource by name and type only (config: dict (15 items)). The rest of /meta (start time, routes, host, process) is unchanged, so deploy.sh's smoke test still works.
  • GET /v1/logs/feel (the tail of the front-end error log, with usernames and error payloads) had no permission check; it now requires a maintainer, like /logs/api and /logs/api_exc.

Tests: test_meta_shows_no_config_values (no config value in /meta/ or /meta/json/, the key config still listed) and test_frontend_error_log_maintainers_only (a non-maintainer coordinator gets 403). Both fail without the change; full suite 50 passed, 1 xfailed.

Written with Claude (Claude Code) on behalf of @lgelauff.

🤖 Generated with Claude Code

…tainers only

/meta and /meta/json/ are public. clastic's resource section shows the
first 70 characters of repr() of each app resource, which for 'config'
showed the start of the config dict to anyone. The resource section now
lists each resource by name and type only (ResourceNamesPeripheral);
the rest of /meta (start time, routes, host, process) is unchanged, so
deploy.sh's smoke test keeps working.

GET /v1/logs/feel (the front-end error log tail: usernames and error
payloads) had no permission check; it now requires a maintainer, like
/logs/api and /logs/api_exc.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mahmoud
mahmoud merged commit 9b862b1 into master Oct 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants