…file [CLI-1986]
A profile is a named settings file in the configstore's profiles directory,
next to the default configuration. --config-profile, or SNYK_CONFIG_PROFILE
when the flag is not given, selects the profile for the command. The flag is
not called --profile, because `snyk mcp` already has a flag of that name.
- The engine runs the root invocations of the command on the selected
profile. Without a profile the run is unchanged, the registry is only
enabled when a profile is requested.
- The command's own settings (input directory, raw arguments, the presenter
of test commands) are set on the profile too, because a profile is derived
from the configuration of the run and does not carry values set afterwards.
- The analytics, the instrumentation, the debug log footer and its token
fingerprint use the credentials and host of the profile. A profile that
cannot be used fails the command with a validation error and reports
nothing.
- The legacy CLI reads only the default configuration file, so it is refused
for a profile other than the default one.
Known limitation: environment variables such as SNYK_TOKEN still apply to
every profile. A test pins this until environment blocking lands.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Canary branch. It carries the CLI work under test plus one temporary commit that pins an unreleased go-application-framework commit, so the CLI CI shows early whether the framework work breaks the CLI. It is rebuilt regularly and never merged.
🤖 Generated with Claude Code