Repository navigation
Added concurrent update and hybrid scanning settings to agent_config.edit - #1043
Merged
Merged
Conversation
The edit() docstring linked to the agent-config-details reference page and details() linked to agent-config-edit. Each now links to its own page.
…edit (RDC-25175) agent_config.edit() now accepts keyword-only concurrent_update, max_concurrent_update and hybrid_scanning_enabled arguments, sent in the agent-config-edit request body. max_concurrent_update is validated as an integer from 0 to 2500 before the request is sent, and the booleans are validated with _check(). Only the settings passed are sent. Live testing showed that the API merges a partial body into the existing configuration, including the nested concurrent_update object, so omitted settings keep their values; the docstring says so.
SteveMcGrath
approved these changes
Oct 12, 2026
Contributor
|
unsubscribe
…On Mon, Oct 12, 2026 at 11:45 PM Steven McGrath ***@***.***> wrote:
Merged #1043 <#1043> into main.
—
Reply to this email directly, view it on GitHub
<#1043?email_source=notifications&email_token=ACPWV3L5M5UPYVXNBRYDJQT5TUNMJA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMZQGU4TIOBQHA4TFJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#event-33059480892>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACPWV3OLVPTLSYPQQP3OV235TUNMJAVCNFSNUABFKJSXA33TNF2G64TZHMYTCNBWHA4TAOJQHNEXG43VMU5TKNRZGY2TSNJQGQ22C5QC>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/ACPWV3J63GB7ULVD3YAUSRT5TUNMJA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMZQGU4TIOBQHA4TFJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG>
and Android
<https://github.com/notifications/mobile/android/ACPWV3KEX5QY4FVMSHOQPCT5TUNMJA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTGMZQGU4TIOBQHA4TFJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
Download it today!
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
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.
Description
This adds the documented
concurrent_updateandhybrid_scanning_enabledsettings ofPUT /scanners/null/agents/configtotio.agent_config.edit().concurrent_updatewas announced in Concurrent Update Settings for Sensor Configurations (2026-01-27). This PR also fixes the module's two:devportal:links, which pointed at each other's pages.edit()now links toagent-config-edit, anddetails()toagent-config-details.concurrent_update(bool),max_concurrent_update(int, 0–2500) andhybrid_scanning_enabled(bool).Design notes:
max_concurrent_updateis separate from theconcurrent_updateswitch, because0is a valid limit: it stops agents from updating plugins. The single-integer style ofauto_unlinkwould read0as "disable".concurrent_update. Soedit(max_concurrent_update=0)changes only the limit, and the docstring says unspecified settings keep their values.max_concurrent_updatemust be anint, notbool, from 0 to 2500, checked before the request is sent. The booleans use the module's existing_check().auto_unlinkobject, which the API ignores.No new dependencies.
CHANGELOG.mdandtenable/version.pyare untouched.Fixes #1042
Internal tracking: RDC-25175.
Type of change
How Has This Been Tested?
Unit tests. They use
responsesand add no cassettes. They assert the exact request body withjson_params_matcher(..., strict_match=True).max_concurrent_updateat 0 and 2500;software_updateandauto_unlink;max_concurrent_updateof 2501 or -1 raisesUnexpectedValueError. A string or bool raisesTypeError. Invalid booleans raiseTypeError. None of these sends a request.main: every test that sends a new value, and both range checks, fail againstmain. The no-arguments case passes there because the request is unchanged.ruff check tenableis clean, andruff formatreports no changes inagent_config.py. The full suite passes on 3.11, 3.12, 3.13 and 3.14: 2190 passed, 0 failed, 95.6–95.8% coverage, and no new cassettes.bandit -llresults are unchanged frommain(no medium or high issues).main(the same 6 warnings). The new arguments render, and both reference links point to the right pages.Live API tests. These used the patched methods against three Tenable Vulnerability Management test environments. The agent configuration is a single account-wide setting, so each test recorded the original configuration first, restored it in a
finallyblock, and verified the restored configuration was identical. All 15 checks passed in each environment:edit(concurrent_update=True, max_concurrent_update=123)applied both values and left every other setting unchanged. The response matcheddetails().edit(max_concurrent_update=0)keptenabled=True;edit(concurrent_update=False)kept the limit of0.edit(hybrid_scanning_enabled=...)toggled the setting both ways without touchingconcurrent_update.edit()with no arguments, and with only the existingsoftware_updateargument, left the configuration as it was.edit(): passing the original values toedit()reproduced the original configuration exactly.Test Configuration:
Checklist: