KC-1478: Fix false 'Supported columns' warning in enterprise-info when requesting base fields - #2397
Merged
Merged
Conversation
…ing base fields (#2396)
craiglurey
approved these changes
Sep 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix
enterprise-info --columnsprinting a false "Supported X columns" warning when the requested columns include a field that's always present in the output (user_id/emailfor users,team_uid/namefor teams,node_id/namefor nodes,role_id/namefor roles) but isn't in the optionalSUPPORTED_*_COLUMNSvalidation list. The command already succeeded and returned the field correctly — only the warning was wrong.Changes
keepercommander/commands/enterprise.py:BASE_NODE_COLUMNS,BASE_USER_COLUMNS,BASE_TEAM_COLUMNS,BASE_ROLE_COLUMNSsets identifying the fields always included in each row regardless of--columnsunit-tests/test_command_enterprise.py:user_id,email,team_uid,node_id,role_id,name) no longer trigger the warning