[PR #10] [MERGED] Policies Progress and added MongoDB to docker setup #1489

Closed
opened 2026-03-02 02:23:31 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/amidaware/tacticalrmm/pull/10
Author: @sadnub
Created: 4/19/2020
Status: Merged
Merged: 4/19/2020
Merged by: @wh1te909

Base: developHead: feature-policies-alerts


📝 Commits (3)

  • 8a22299 Policy Overview Add/Edit
  • 5588f90 Added most framework for Policies in Checks and Tasks. Added MongoDB to docker setup and configured for MeshCentral
  • 58fb862 Merge branch 'develop' into feature-policies-alerts

📊 Changes

42 files changed (+1880 additions, -169 deletions)

View changed files

📝 api/tacticalrmm/agents/urls.py (+1 -0)
📝 api/tacticalrmm/agents/views.py (+5 -0)
📝 api/tacticalrmm/automation/serializers.py (+21 -4)
📝 api/tacticalrmm/automation/urls.py (+3 -1)
📝 api/tacticalrmm/automation/views.py (+77 -9)
api/tacticalrmm/checks/migrations/0006_auto_20200415_0300.py (+45 -0)
api/tacticalrmm/checks/migrations/0007_auto_20200415_2300.py (+45 -0)
api/tacticalrmm/checks/migrations/0011_merge_20200416_1658.py (+14 -0)
api/tacticalrmm/checks/migrations/0012_auto_20200419_1900.py (+76 -0)
📝 api/tacticalrmm/checks/models.py (+84 -32)
📝 api/tacticalrmm/checks/serializers.py (+24 -0)
📝 api/tacticalrmm/checks/urls.py (+1 -0)
📝 api/tacticalrmm/checks/views.py (+37 -17)
📝 api/tacticalrmm/clients/serializers.py (+5 -1)
📝 api/tacticalrmm/clients/urls.py (+1 -0)
📝 api/tacticalrmm/clients/views.py (+5 -0)
📝 docker/.env.example (+3 -0)
📝 docker/docker-compose.dev.yml (+4 -4)
📝 docker/docker-compose.yml (+16 -0)
📝 docker/meshcentral/config.json (+29 -28)

...and 22 more files

📄 Description

Here is a progress commit. I wasn't able to test everything out, but I don't think the code would have affected the agent table at all.

I wasn't sure how to handle the agent.hostname dependency on the checks models. I have a solution in place, but I'm not sure if this will mess anything up. It is a start at least!

Next thing I need to do is finish up the automation overview and provide some visibility into the agents affected by the policies and be able to view the individual output for the checks.


🔄 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/10 **Author:** [@sadnub](https://github.com/sadnub) **Created:** 4/19/2020 **Status:** ✅ Merged **Merged:** 4/19/2020 **Merged by:** [@wh1te909](https://github.com/wh1te909) **Base:** `develop` ← **Head:** `feature-policies-alerts` --- ### 📝 Commits (3) - [`8a22299`](https://github.com/amidaware/tacticalrmm/commit/8a22299998426a4e11e4c33860c59d3b1271cfe5) Policy Overview Add/Edit - [`5588f90`](https://github.com/amidaware/tacticalrmm/commit/5588f901b5c4f3eab2543e3af40e77d477fe16e1) Added most framework for Policies in Checks and Tasks. Added MongoDB to docker setup and configured for MeshCentral - [`58fb862`](https://github.com/amidaware/tacticalrmm/commit/58fb862d4a4d6b35dabb87fd17b5ed382e214b41) Merge branch 'develop' into feature-policies-alerts ### 📊 Changes **42 files changed** (+1880 additions, -169 deletions) <details> <summary>View changed files</summary> 📝 `api/tacticalrmm/agents/urls.py` (+1 -0) 📝 `api/tacticalrmm/agents/views.py` (+5 -0) 📝 `api/tacticalrmm/automation/serializers.py` (+21 -4) 📝 `api/tacticalrmm/automation/urls.py` (+3 -1) 📝 `api/tacticalrmm/automation/views.py` (+77 -9) ➕ `api/tacticalrmm/checks/migrations/0006_auto_20200415_0300.py` (+45 -0) ➕ `api/tacticalrmm/checks/migrations/0007_auto_20200415_2300.py` (+45 -0) ➕ `api/tacticalrmm/checks/migrations/0011_merge_20200416_1658.py` (+14 -0) ➕ `api/tacticalrmm/checks/migrations/0012_auto_20200419_1900.py` (+76 -0) 📝 `api/tacticalrmm/checks/models.py` (+84 -32) 📝 `api/tacticalrmm/checks/serializers.py` (+24 -0) 📝 `api/tacticalrmm/checks/urls.py` (+1 -0) 📝 `api/tacticalrmm/checks/views.py` (+37 -17) 📝 `api/tacticalrmm/clients/serializers.py` (+5 -1) 📝 `api/tacticalrmm/clients/urls.py` (+1 -0) 📝 `api/tacticalrmm/clients/views.py` (+5 -0) 📝 `docker/.env.example` (+3 -0) 📝 `docker/docker-compose.dev.yml` (+4 -4) 📝 `docker/docker-compose.yml` (+16 -0) 📝 `docker/meshcentral/config.json` (+29 -28) _...and 22 more files_ </details> ### 📄 Description Here is a progress commit. I wasn't able to test everything out, but I don't think the code would have affected the agent table at all. I wasn't sure how to handle the agent.hostname dependency on the checks models. I have a solution in place, but I'm not sure if this will mess anything up. It is a start at least! Next thing I need to do is finish up the automation overview and provide some visibility into the agents affected by the policies and be able to view the individual output for the checks. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-02 02:23:31 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#1489
No description provided.