SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-27 10:32:09 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

[PR #1801] [MERGED] [Diagnostic] Introduced optional lxc install diagnostics via API call #3219

New Issue
Closed
opened 2025-11-20 06:03:37 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 06:03:37 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/1801
Author: @michelroegl-brunner
Created: 1/28/2025
Status: ✅ Merged
Merged: 1/29/2025
Merged by: @MickLesk

Base: main ← Head: api

📝 Commits (10+)

📊 Changes

1 file changed (+215 additions, -76 deletions)

View changed files

📝 misc/build.func (+215 -76)

📄 Description

✍️ Description

This PR implements a feature to call to a API to save diagnostics. No User Data will get send and a user needs to Opt-In during LXC creation.

Related Discussion: #1836

✅ Prerequisites

The following steps must be completed for the pull request to be considered:

  • Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.)
  • Testing performed (I have thoroughly tested my changes and verified expected functionality.)

🛠️ Type of Change

Please check the relevant options:

  • [] Bug fix (non-breaking change that resolves an issue)
  • New feature (non-breaking change that adds functionality)
  • [] Breaking change (fix or feature that would cause existing functionality to change unexpectedly)
  • [] New script (a fully functional and thoroughly tested script or set of scripts)

📋 Additional Information (optional)

The Database ist hosted in the Datacenter of the school i work for and is maintained by myself.

  • First use on a Proxmox node
    image

  • New menu
    image

  • Diagnostic Settings
    image
    image

🔄 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/1801 **Author:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Created:** 1/28/2025 **Status:** ✅ Merged **Merged:** 1/29/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `api` --- ### 📝 Commits (10+) - [`00cd62f`](https://github.com/community-scripts/ProxmoxVE/commit/00cd62fc384098e394cf6170e3d920c9f142495b) Update build.func - [`c04ec81`](https://github.com/community-scripts/ProxmoxVE/commit/c04ec818fea547b2a9e584c1f95e1b3266f49ef4) Update build.func - [`3677d11`](https://github.com/community-scripts/ProxmoxVE/commit/3677d116fb219c83166af081d70404cf423e2029) Update build.func - [`08286bc`](https://github.com/community-scripts/ProxmoxVE/commit/08286bc9993376a3d19f4480fa4447dc1da733fe) Update build.func - [`64acc43`](https://github.com/community-scripts/ProxmoxVE/commit/64acc43716195613315d2386b8157c3056904965) Merge branch 'api' of https://github.com/community-scripts/ProxmoxVE into api - [`deaf691`](https://github.com/community-scripts/ProxmoxVE/commit/deaf6918e98257ab412a145a563c336cc975f14f) Update build.func - [`2d43fde`](https://github.com/community-scripts/ProxmoxVE/commit/2d43fde119f2939e78e3d74e5d2b736d694822c9) update build.func - [`acd502c`](https://github.com/community-scripts/ProxmoxVE/commit/acd502cda32c40d97fbf111bfb4c361f09171792) update build.func - [`3de219f`](https://github.com/community-scripts/ProxmoxVE/commit/3de219f4cf201f6460ddfde4974879e95a77e245) update build.func - [`f7ebb40`](https://github.com/community-scripts/ProxmoxVE/commit/f7ebb403391dbf92b376f953b9d5c8a8b5f09bc2) update build.func ### 📊 Changes **1 file changed** (+215 additions, -76 deletions) <details> <summary>View changed files</summary> 📝 `misc/build.func` (+215 -76) </details> ### 📄 Description ## ✍️ Description This PR implements a feature to call to a API to save diagnostics. **No User Data will get send** and a user needs to Opt-In during LXC creation. - - - Related Discussion: #1836 --- ## ✅ Prerequisites The following steps must be completed for the pull request to be considered: - [X] Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.) - [X] Testing performed (I have thoroughly tested my changes and verified expected functionality.) ## 🛠️ Type of Change Please check the relevant options: - [] Bug fix (non-breaking change that resolves an issue) - [X] New feature (non-breaking change that adds functionality) - [] Breaking change (fix or feature that would cause existing functionality to change unexpectedly) - [] New script (a fully functional and thoroughly tested script or set of scripts) --- ## 📋 Additional Information (optional) The Database ist hosted in the Datacenter of the [school](www-htl-braunau.at) i work for and is maintained by myself. - First use on a Proxmox node ![image](https://github.com/user-attachments/assets/455dcde0-19f9-479f-9ef2-9d2bd6c6d690) - New menu ![image](https://github.com/user-attachments/assets/667aed81-e68f-4ce5-a4d6-534ac318af1a) - Diagnostic Settings ![image](https://github.com/user-attachments/assets/dc9d75a8-165a-4857-a29e-47fb1d8c0e1e) ![image](https://github.com/user-attachments/assets/6177a054-06d1-4833-8dfa-feb36e756a60) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2025-11-20 06:03:37 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#3219
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?