-
Notifications
You must be signed in to change notification settings - Fork 79
Comparing changes
Open a pull request
base repository: Keeper-Security/Commander
base: v17.1.10
head repository: Keeper-Security/Commander
compare: v17.1.11
- 15 commits
- 45 files changed
- 8 contributors
Commits on Oct 2, 2025
-
Improved pam legacy command to toggle Legacy mode ON/OFF (#1599)
* Improved pam legacy command to toggle legacy mode ON/OFF * Added --status option to print current state * Improved keeper_dag vertex logging
Configuration menu - View commit details
-
Copy full SHA for bae49e0 - Browse repository at this point
Copy the full SHA bae49e0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1a3b899 - Browse repository at this point
Copy the full SHA 1a3b899View commit details -
Fixed IAM User rotation (#1602)
IAM User rotation should not convert to General rotation on update
Configuration menu - View commit details
-
Copy full SHA for 2ec800d - Browse repository at this point
Copy the full SHA 2ec800dView commit details -
Configuration menu - View commit details
-
Copy full SHA for e45753d - Browse repository at this point
Copy the full SHA e45753dView commit details -
Service Mode Response Updates (#1601)
* Update error responses to be consistent * Update response for commands where logs are generated and flags are mandatory * Update readme with correct errors handled and Code clean/ refactor. * Update service-mode unit-tests
Configuration menu - View commit details
-
Copy full SHA for dde375e - Browse repository at this point
Copy the full SHA dde375eView commit details -
Configuration menu - View commit details
-
Copy full SHA for b1d41ad - Browse repository at this point
Copy the full SHA b1d41adView commit details -
fix: Complete argument parsing fix for commands with global arguments
This commit fixes the argument parsing issue introduced in commit 8100dc2 where global arguments (like --config, --server, --debug) appearing after command names were incorrectly passed to subcommand parsers. The fix: - Preserves original argument order to maintain proper flag/value pairing - Filters out all main parser arguments before reconstruction - Handles both --arg=value and --arg value formats - Properly quotes all arguments using shlex.quote() Fixes commands like: - keeper record-add --config='config.json' -t 'Title' -rt login ... - keeper record-add --debug --server='host' -t 'Title' ... This resolves the 'unrecognized arguments' errors while maintaining the original fix for service-create command issues.
Configuration menu - View commit details
-
Copy full SHA for 7aaeaf3 - Browse repository at this point
Copy the full SHA 7aaeaf3View commit details -
Added Support for Cloudflare in Service Mode
# Conflicts: # keepercommander/service/core/service_manager.py
Configuration menu - View commit details
-
Copy full SHA for 023eff9 - Browse repository at this point
Copy the full SHA 023eff9View commit details -
Configuration menu - View commit details
-
Copy full SHA for d0a4dfa - Browse repository at this point
Copy the full SHA d0a4dfaView commit details -
Our Lambda handler script returns an error in production, due to two problems with the script: By default, Lambda file system cannot file to → We import keepercommander without setting HOME, TMPDIR and TEMP environment variables, which would cause an issue as it would create pycache in user directory. → We call api.login(), which will attempt to create a .keeper/config.json file in user directory - which Lambda isn't allowed to do. This change request introduces the following: Complete overhaul of the lambda handler script -Added HOME, TMPDIR and TEMP environment variables before import -Added code that creates custom /tmp/.keeper/ dir to store the config file. -Added code that leverages the get_params_from_config() function to store the config file in custom /tmp/.keeper/ dir. -Removed email handler function as it was useful but not on topic for Keeper SDK. Replaced it with more basic functions specific to Keeper SDK. Reworked the step by step explanation of the program to fit the overhaul. The Layer Content script is also outdated by hoping to get some help from Commander contributors for this.
Configuration menu - View commit details
-
Copy full SHA for 473630d - Browse repository at this point
Copy the full SHA 473630dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1cb7fa8 - Browse repository at this point
Copy the full SHA 1cb7fa8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3e722e0 - Browse repository at this point
Copy the full SHA 3e722e0View commit details -
Configuration menu - View commit details
-
Copy full SHA for dd30400 - Browse repository at this point
Copy the full SHA dd30400View commit details -
Configuration menu - View commit details
-
Copy full SHA for 64da693 - Browse repository at this point
Copy the full SHA 64da693View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1bae535 - Browse repository at this point
Copy the full SHA 1bae535View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v17.1.10...v17.1.11