[PR #7619] [MERGED] pdm: refactor for beta version #6946

Closed
opened 2026-02-26 15:33:33 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/7619
Author: @CrazyWolf13
Created: 9/13/2025
Status: Merged
Merged: 9/13/2025
Merged by: @MickLesk

Base: mainHead: CrazyWolf13-patch-3


📝 Commits (2)

  • 46b91f6 pdm: refactor for beta version
  • 063cf40 pdm: refactor for beta and deb13 preparation

📊 Changes

2 files changed (+18 additions, -6 deletions)

View changed files

📝 ct/proxmox-datacenter-manager.sh (+11 -1)
📝 install/proxmox-datacenter-manager-install.sh (+7 -5)

📄 Description

✍️ Description

Refactor Proxmox-Datacenter-manager for upgrade to beta and prepare for simpler deb13 migration.

EDIT: yes the trixie key seems to work fine, the only reason to use is so the migration from alpha to beta works much better, because otherwise it's a repo and a key change which I had issues without previously adding the new key.

It is recommended to do the migration to deb13 directly from alpha to beta migration, shall this be included directly or not?

Link: #

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 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/community-scripts/ProxmoxVE/pull/7619 **Author:** [@CrazyWolf13](https://github.com/CrazyWolf13) **Created:** 9/13/2025 **Status:** ✅ Merged **Merged:** 9/13/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `CrazyWolf13-patch-3` --- ### 📝 Commits (2) - [`46b91f6`](https://github.com/community-scripts/ProxmoxVE/commit/46b91f64cec85a5c839ede1840ef47dafbd7e33d) pdm: refactor for beta version - [`063cf40`](https://github.com/community-scripts/ProxmoxVE/commit/063cf40830fe527db9afa275167b401a86342339) pdm: refactor for beta and deb13 preparation ### 📊 Changes **2 files changed** (+18 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `ct/proxmox-datacenter-manager.sh` (+11 -1) 📝 `install/proxmox-datacenter-manager-install.sh` (+7 -5) </details> ### 📄 Description <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ Description Refactor Proxmox-Datacenter-manager for upgrade to beta and prepare for simpler deb13 migration. EDIT: yes the trixie key seems to work fine, the only reason to use is so the migration from alpha to beta works much better, because otherwise it's a repo and a key change which I had issues without previously adding the new key. It is recommended to do the migration to deb13 directly from alpha to beta migration, shall this be included directly or not? ## 🔗 Related PR / Issue Link: # ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [ ] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [x] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 15:33:33 +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/ProxmoxVE#6946
No description provided.