Skip to content

Conversation

@dc-larsen
Copy link
Contributor

Summary

  • Adds an INFO-level log message that tells users where the configuration is being loaded from
  • Tracks the config source internally via a _config_source key
  • Outputs user-friendly descriptions for each source type

Config Sources

The three possible sources (in priority order) are:

  1. Socket dashboard (API) - when using enterprise plan with dashboard config
  2. JSON config file (--config) - when a config file is specified via CLI
  3. Environment variables - the default when no other source is available

Example Output

2024-01-06 13:20:00 - INFO - Configuration loaded from: Socket dashboard (API)

or

2024-01-06 13:20:00 - INFO - Configuration loaded from: environment variables

Test plan

  • Run socket-basics with no config (should show "environment variables")
  • Run socket-basics with --config config.json (should show "JSON config file")
  • Run socket-basics with API key and enterprise org (should show "Socket dashboard (API)")

🤖 Generated with Claude Code

Adds an INFO-level log message that tells users where the configuration
is being loaded from. The three possible sources are:

1. Socket dashboard (API) - when using enterprise plan with dashboard config
2. JSON config file (--config) - when a config file is specified via CLI
3. Environment variables - the default when no other source is available

This helps users debug configuration issues by making it clear which
source took precedence.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@dc-larsen dc-larsen requested a review from a team as a code owner January 6, 2026 21:34
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.

2 participants