[PR #2301] [MERGED] Windows Registry support #3871

New issue

Closed

opened 2026-03-14 07:43:25 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 07:43:25 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/amidaware/tacticalrmm/pull/2301
Author: @fahadkhan-fk
Created: 10/2/2025
Status: ✅ Merged
Merged: 12/29/2025
Merged by: @wh1te909

Base: develop ← Head: feature-registry

📝 Commits (10+)

2b04ed1 feat: add endpoints related to browse, create and delete registry key
dc75137 feat: get path from query params
ac90905 feat: add endpoint related to renaming key in registry
12206d0 feat: add endpoints related to create,delete,rename and modify value
cd3d74f feat: enhance registry APIs
b4d83e3 feat: add tests related to registry
0166f7c feat: add can_use_registry permission in manager
adfbb0e Fix: resolve migration conflict and reapply can_use_registry field
42f4be1 add perms and add defer
ae18a9b add version check

📊 Changes

7 files changed (+727 additions, -1 deletions)

View changed files

➕ api/tacticalrmm/accounts/migrations/0040_role_can_use_registry.py (+18 -0)
📝 api/tacticalrmm/accounts/models.py (+1 -0)
📝 api/tacticalrmm/agents/permissions.py (+10 -0)
➕ api/tacticalrmm/agents/tests/test_registry.py (+364 -0)
📝 api/tacticalrmm/agents/urls.py (+36 -0)
📝 api/tacticalrmm/agents/utils.py (+41 -1)
📝 api/tacticalrmm/agents/views.py (+257 -0)

📄 Description

No description provided

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/amidaware/tacticalrmm/pull/2301 **Author:** [@fahadkhan-fk](https://github.com/fahadkhan-fk) **Created:** 10/2/2025 **Status:** ✅ Merged **Merged:** 12/29/2025 **Merged by:** [@wh1te909](https://github.com/wh1te909) **Base:** `develop` ← **Head:** `feature-registry` --- ### 📝 Commits (10+) - [`2b04ed1`](https://github.com/amidaware/tacticalrmm/commit/2b04ed16dde39e35de7824b33e6123921aefec2a) feat: add endpoints related to browse, create and delete registry key - [`dc75137`](https://github.com/amidaware/tacticalrmm/commit/dc75137dc5e2c2c2d6dce11c0e9206bcd2d00973) feat: get path from query params - [`ac90905`](https://github.com/amidaware/tacticalrmm/commit/ac90905ab7becbf6dabc139f85c0b45e51af54cd) feat: add endpoint related to renaming key in registry - [`12206d0`](https://github.com/amidaware/tacticalrmm/commit/12206d07ca3c3ea3696c8e989dea0dbf6d5c3196) feat: add endpoints related to create,delete,rename and modify value - [`cd3d74f`](https://github.com/amidaware/tacticalrmm/commit/cd3d74fef3b6c885103f124c9b87a6c92f971fb8) feat: enhance registry APIs - [`b4d83e3`](https://github.com/amidaware/tacticalrmm/commit/b4d83e339ff2e492587f06b44cf1b377c9dbeae7) feat: add tests related to registry - [`0166f7c`](https://github.com/amidaware/tacticalrmm/commit/0166f7ca062d72ae17e59b26fc03d64df2cae922) feat: add can_use_registry permission in manager - [`adfbb0e`](https://github.com/amidaware/tacticalrmm/commit/adfbb0e44a75a59fee69bfcc59235a5f5cf75ad3) Fix: resolve migration conflict and reapply can_use_registry field - [`42f4be1`](https://github.com/amidaware/tacticalrmm/commit/42f4be1fa9fed2de90e7cf81c8b48bc6ea4ee773) add perms and add defer - [`ae18a9b`](https://github.com/amidaware/tacticalrmm/commit/ae18a9bb769292d0504d19c4ce050dbb9b21ad06) add version check ### 📊 Changes **7 files changed** (+727 additions, -1 deletions) <details> <summary>View changed files</summary> ➕ `api/tacticalrmm/accounts/migrations/0040_role_can_use_registry.py` (+18 -0) 📝 `api/tacticalrmm/accounts/models.py` (+1 -0) 📝 `api/tacticalrmm/agents/permissions.py` (+10 -0) ➕ `api/tacticalrmm/agents/tests/test_registry.py` (+364 -0) 📝 `api/tacticalrmm/agents/urls.py` (+36 -0) 📝 `api/tacticalrmm/agents/utils.py` (+41 -1) 📝 `api/tacticalrmm/agents/views.py` (+257 -0) </details> ### 📄 Description _No description provided_ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>