Skip to content

Remove CLI scope and support unresolved variable selection - #144

Merged
rsgalloway merged 1 commit into
masterfrom
issue131/remove-cli-scope
Oct 17, 2026
Merged

rsgalloway merged 1 commit into
masterfrom
issue131/remove-cli-scope

Conversation

@rsgalloway

@rsgalloway rsgalloway commented Oct 17, 2026 •

Copy link
Copy Markdown
Owner

This pull request improves the CLI experience for selecting and displaying unresolved environment variables, updates documentation to match the new interface, removes an unused CLI option, and refines related test cases. The main changes include allowing -u/--unresolved to accept variable names (like -r/--resolve), requiring stack names before these options, and removing the unused --scope CLI option.

CLI and API Improvements

  • The -u/--unresolved CLI option now accepts zero or more variable names, matching the behavior of -r/--resolve. If no variable names are given, all unresolved values are shown; if variable names are given, only those are displayed. The option must follow the stack name (e.g., envstack dev -u VAR). The -q/--quiet flag now only works if exactly one variable is selected. [1] [2]

  • The unused CLI --scope option is removed; use the ENVPATH environment variable to select stack search directories instead. The Python API scope parameter remains supported.

Documentation Updates

  • Updated README.md, docs/index.md, and docs/api.md to document the new behavior for -u/--unresolved, including examples and usage notes. [1] [2] [3]

Tests

  • Added new tests in tests/test_cli.py to cover variable selection, quiet mode, unknown variables, and repeated options for the new -u/--unresolved behavior.

  • Updated existing tests in tests/test_cmds.py to use the new argument order and behavior for unresolved variable selection. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

@rsgalloway rsgalloway self-assigned this Oct 17, 2026
@rsgalloway rsgalloway added bug Something isn't working enhancement New feature or request labels Oct 17, 2026
@rsgalloway rsgalloway added this to the Version 1.0.5 milestone Oct 17, 2026
@rsgalloway rsgalloway linked an issue Oct 17, 2026 that may be closed by this pull request
@rsgalloway
rsgalloway requested a lite review from Copilot October 17, 2026 16:07

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No unresolved blocking issues were identified.

No open issues 🎉

What changed in this PR

Updates CLI unresolved-variable selection, removes the unused --scope option, and refreshes related documentation and tests.

Changes:

  • Adds variable filtering and quiet output for -u/--unresolved.
  • Requires stack names before selection options.
  • Removes CLI --scope while retaining API support.
  • Updates tests, documentation, and changelog.
File Description
tests/​test_cmds.py Updates command invocation syntax.
tests/​test_cli.py Adds coverage for selection and quiet mode.
README.md Documents unresolved selection.
lib/​envstack/​cli.py Implements the CLI behavior changes.
docs/​index.md Updates CLI usage documentation.
docs/​api.md Documents selection and quiet behavior.
CHANGELOG.md Records the interface changes.

Review effort: Lite

@rsgalloway
rsgalloway merged commit 69d3fd4 into master Oct 17, 2026
45 checks passed
@rsgalloway
rsgalloway deleted the issue131/remove-cli-scope branch October 17, 2026 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

remove the obsolete CLI --scope option

2 participants