remove_local_account_keys = None, next to the personal-account actions QTS already switches off. See NetOrk/netork#2013.
napalm-device-types (NAPALM/napalm-device-types#90, assumed to be 4.28.0) adds remove_local_account_keys to LocalAccountsMixin, and napalm-linux (NAPALM/napalm-linux#69, assumed to be 0.17.0) brings it to every LinuxDriver. QTS manages its users in its own UI. Without this line, a capability check (callable(getattr(driver, "remove_local_account_keys", None))) would say QTS can take keys off an account. The opt-out is still in place for get_local_accounts, add_local_account, lock_local_account and add_service_account, so replaces and clear_password cannot reach QTS.
Needs the releases first. The floors are raised to napalm-device-types>=4.28.0 and napalm-linux>=0.17.0, because the test also asserts that LinuxDriver has the method.
Tests
Fixtures only. test_personal_accounts_are_not_managed_here now includes remove_local_account_keys. It failed first against the new device-types (the method was callable on QnapQtsDriver). 116 tests pass, ruff, napalm-standard check and ratchet are clean, and mypy reports nothing in napalm_qnap_qts.
## What
`remove_local_account_keys = None`, next to the personal-account actions QTS already switches off. See NetOrk/netork#2013.
napalm-device-types (NAPALM/napalm-device-types#90, assumed to be 4.28.0) adds `remove_local_account_keys` to `LocalAccountsMixin`, and napalm-linux (NAPALM/napalm-linux#69, assumed to be 0.17.0) brings it to every `LinuxDriver`. QTS manages its users in its own UI. Without this line, a capability check (`callable(getattr(driver, "remove_local_account_keys", None))`) would say QTS can take keys off an account. The opt-out is still in place for `get_local_accounts`, `add_local_account`, `lock_local_account` and `add_service_account`, so `replaces` and `clear_password` cannot reach QTS.
**Needs the releases first.** The floors are raised to `napalm-device-types>=4.28.0` and `napalm-linux>=0.17.0`, because the test also asserts that `LinuxDriver` has the method.
## Tests
Fixtures only. `test_personal_accounts_are_not_managed_here` now includes `remove_local_account_keys`. It failed first against the new device-types (the method was callable on `QnapQtsDriver`). 116 tests pass, ruff, `napalm-standard check` and `ratchet` are clean, and mypy reports nothing in `napalm_qnap_qts`.
napalm-linux 0.17.0 brings napalm-device-types' new
remove_local_account_keys to every LinuxDriver. QTS has the other
personal-account actions switched off, as it manages its users in its
own UI; without this one a capability check would say QTS can take keys
off an account.
See NetOrk/netork#2013
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
remove_local_account_keys = None, next to the personal-account actions QTS already switches off. See NetOrk/netork#2013.napalm-device-types (NAPALM/napalm-device-types#90, assumed to be 4.28.0) adds
remove_local_account_keystoLocalAccountsMixin, and napalm-linux (NAPALM/napalm-linux#69, assumed to be 0.17.0) brings it to everyLinuxDriver. QTS manages its users in its own UI. Without this line, a capability check (callable(getattr(driver, "remove_local_account_keys", None))) would say QTS can take keys off an account. The opt-out is still in place forget_local_accounts,add_local_account,lock_local_accountandadd_service_account, soreplacesandclear_passwordcannot reach QTS.Needs the releases first. The floors are raised to
napalm-device-types>=4.28.0andnapalm-linux>=0.17.0, because the test also asserts thatLinuxDriverhas the method.Tests
Fixtures only.
test_personal_accounts_are_not_managed_herenow includesremove_local_account_keys. It failed first against the new device-types (the method was callable onQnapQtsDriver). 116 tests pass, ruff,napalm-standard checkandratchetare clean, and mypy reports nothing innapalm_qnap_qts.