starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-07-16 04:03:50 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

[PR #1811] [MERGED] Allow admins to "lock" allocations #1583

New Issue
Closed
opened 2026-02-05 18:18:20 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 18:18:20 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/panel/pull/1811
Author: @Boy132
Created: 10/14/2025
Status: ✅ Merged
Merged: 11/8/2025
Merged by: @Boy132

Base: main ← Head: boy132/allocation-marker

📝 Commits (4)

  • d81294a add allocation locking
  • 67c0461 Merge branch 'main' into boy132/allocation-marker
  • 5e6b255 add missing tooltip
  • e3f3226 make sure allocation is unlocked when removed from server

📊 Changes

7 files changed (+93 additions, -7 deletions)

View changed files

📝 app/Filament/Admin/Resources/Servers/RelationManagers/AllocationsRelationManager.php (+36 -5)
📝 app/Filament/Server/Resources/Allocations/AllocationResource.php (+9 -2)
📝 app/Models/Allocation.php (+13 -0)
📝 app/Services/Servers/ServerCreationService.php (+1 -0)
➕ database/migrations/2025_10_14_065517_add_is_locked_to_allocations.php (+28 -0)
📝 lang/en/admin/server.php (+4 -0)
📝 lang/en/server/network.php (+2 -0)

📄 Description

Closes #1740

If an allocation is locked it can't be removed on the client area/ by normal users. When admins assign allocations to a server they are locked by default but can also be manually locked/ unlocked.

🔄 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/pelican-dev/panel/pull/1811 **Author:** [@Boy132](https://github.com/Boy132) **Created:** 10/14/2025 **Status:** ✅ Merged **Merged:** 11/8/2025 **Merged by:** [@Boy132](https://github.com/Boy132) **Base:** `main` ← **Head:** `boy132/allocation-marker` --- ### 📝 Commits (4) - [`d81294a`](https://github.com/pelican-dev/panel/commit/d81294a5a0e16c2c9c37a192237fb04a7c6ed2d7) add allocation locking - [`67c0461`](https://github.com/pelican-dev/panel/commit/67c0461fd83f1d2be51130415085e5b48354f645) Merge branch 'main' into boy132/allocation-marker - [`5e6b255`](https://github.com/pelican-dev/panel/commit/5e6b255c599a15761b9854d9bee56b40967fc53c) add missing tooltip - [`e3f3226`](https://github.com/pelican-dev/panel/commit/e3f3226276c5127ace52fc0850f83ce1b8ce30c8) make sure allocation is unlocked when removed from server ### 📊 Changes **7 files changed** (+93 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `app/Filament/Admin/Resources/Servers/RelationManagers/AllocationsRelationManager.php` (+36 -5) 📝 `app/Filament/Server/Resources/Allocations/AllocationResource.php` (+9 -2) 📝 `app/Models/Allocation.php` (+13 -0) 📝 `app/Services/Servers/ServerCreationService.php` (+1 -0) ➕ `database/migrations/2025_10_14_065517_add_is_locked_to_allocations.php` (+28 -0) 📝 `lang/en/admin/server.php` (+4 -0) 📝 `lang/en/server/network.php` (+2 -0) </details> ### 📄 Description Closes #1740 If an allocation is locked it can't be removed on the client area/ by normal users. When admins assign allocations to a server they are locked by default but can also be manually locked/ unlocked. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-05 18:18:20 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#1583
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?