github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-03-22 06:11:11 -05:00
Code Issues 258 Packages Projects Releases 10 Wiki Activity

[PR #172] [MERGED] 1.16.9 #705

New Issue
Closed
opened 2025-10-31 15:19:06 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-10-31 15:19:06 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/moghtech/komodo/pull/172
Author: @mbecker20
Created: 11/3/2024
Status: ✅ Merged
Merged: 11/5/2024
Merged by: @mbecker20

Base: main ← Head: 1.16.9

📝 Commits (10+)

  • 1d0e7ec BatchDestroyDeployment
  • 777b845 periphery image pull api
  • 2a957c1 Add Pull apis
  • 1575440 Add PullStack / PullDeployment
  • b44b596 improve init deploy from container
  • 083acec stacks + deployments update_available source
  • a6a2ca7 Fix deploy / destroy stack service
  • 6a43635 updates available indicator
  • 8cece84 add poll for updates and auto update options
  • e574b13 use interval to handle waiting between resource refresh

📊 Changes

90 files changed (+2416 additions, -680 deletions)

View changed files

📝 Cargo.lock (+23 -12)
📝 Cargo.toml (+2 -1)
📝 bin/cli/src/exec.rs (+71 -57)
📝 bin/core/Cargo.toml (+1 -0)
📝 bin/core/src/alert/discord.rs (+32 -11)
📝 bin/core/src/alert/slack.rs (+55 -11)
📝 bin/core/src/api/execute/deployment.rs (+190 -39)
📝 bin/core/src/api/execute/mod.rs (+11 -4)
📝 bin/core/src/api/execute/stack.rs (+102 -4)
📝 bin/core/src/api/read/server.rs (+9 -8)
📝 bin/core/src/api/write/deployment.rs (+99 -4)
📝 bin/core/src/api/write/mod.rs (+1 -0)
📝 bin/core/src/api/write/stack.rs (+71 -52)
📝 bin/core/src/helpers/builder.rs (+3 -1)
📝 bin/core/src/helpers/procedure.rs (+34 -0)
📝 bin/core/src/helpers/query.rs (+1 -1)
📝 bin/core/src/helpers/update.rs (+29 -2)
📝 bin/core/src/listener/resources.rs (+3 -2)
📝 bin/core/src/monitor/helpers.rs (+1 -0)
📝 bin/core/src/monitor/mod.rs (+17 -3)

...and 70 more files

📄 Description

  • Keep images/containers up to date automatically. There are 3 levels depending on how far you want to go for the automation:

    • Manual: (default) - Log in and use the "Pull" execution on Stacks / Deployments to pull latest image, and notify in the UI of an available update.

    • Poll for Update: Pull in the background (default 5 min, use KOMODO_RESOURCE_POLL_INTERVAL to change). If there is an update available, the user will be notified, and an alert will be sent out. It will not deploy the update, preferring to just let the user know for them to do the update at their convenience.

    • Auto Update: Whenever an update is found, it will skip sending an alert, and just go right ahead and redeploy. With this option selected, your running images will be kept up to date totally hands free.

Note that it will only check for newer image at the same tag. If you use a versioned tag, it will not change the tag to a newer one. The intention is that users use latest tags.

🔄 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/moghtech/komodo/pull/172 **Author:** [@mbecker20](https://github.com/mbecker20) **Created:** 11/3/2024 **Status:** ✅ Merged **Merged:** 11/5/2024 **Merged by:** [@mbecker20](https://github.com/mbecker20) **Base:** `main` ← **Head:** `1.16.9` --- ### 📝 Commits (10+) - [`1d0e7ec`](https://github.com/moghtech/komodo/commit/1d0e7ec716aee100ffea3aa2173df37b9453a9c0) BatchDestroyDeployment - [`777b845`](https://github.com/moghtech/komodo/commit/777b845237bdc09c1be4df3d37f66f37d067ef83) periphery image pull api - [`2a957c1`](https://github.com/moghtech/komodo/commit/2a957c128af95469758926fe2a8c96ea30d0e4d0) Add Pull apis - [`1575440`](https://github.com/moghtech/komodo/commit/1575440e832717c8cfbea438a2695349c0a2421f) Add PullStack / PullDeployment - [`b44b596`](https://github.com/moghtech/komodo/commit/b44b596fd1887f3a0a85e9f35b75871a7aee71f6) improve init deploy from container - [`083acec`](https://github.com/moghtech/komodo/commit/083acecb7b51112e8a00cc6b4a7036559f351726) stacks + deployments update_available source - [`a6a2ca7`](https://github.com/moghtech/komodo/commit/a6a2ca72a8d20ca6b116401dd5c526e3aeac4800) Fix deploy / destroy stack service - [`6a43635`](https://github.com/moghtech/komodo/commit/6a436351ebe1e81d05ab932c5b9eef87e9ae29ad) updates available indicator - [`8cece84`](https://github.com/moghtech/komodo/commit/8cece8460bc05f5cee37f4d811eca36a7dd06378) add poll for updates and auto update options - [`e574b13`](https://github.com/moghtech/komodo/commit/e574b13e06bf3b868d643141648869d3b4f42210) use interval to handle waiting between resource refresh ### 📊 Changes **90 files changed** (+2416 additions, -680 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+23 -12) 📝 `Cargo.toml` (+2 -1) 📝 `bin/cli/src/exec.rs` (+71 -57) 📝 `bin/core/Cargo.toml` (+1 -0) 📝 `bin/core/src/alert/discord.rs` (+32 -11) 📝 `bin/core/src/alert/slack.rs` (+55 -11) 📝 `bin/core/src/api/execute/deployment.rs` (+190 -39) 📝 `bin/core/src/api/execute/mod.rs` (+11 -4) 📝 `bin/core/src/api/execute/stack.rs` (+102 -4) 📝 `bin/core/src/api/read/server.rs` (+9 -8) 📝 `bin/core/src/api/write/deployment.rs` (+99 -4) 📝 `bin/core/src/api/write/mod.rs` (+1 -0) 📝 `bin/core/src/api/write/stack.rs` (+71 -52) 📝 `bin/core/src/helpers/builder.rs` (+3 -1) 📝 `bin/core/src/helpers/procedure.rs` (+34 -0) 📝 `bin/core/src/helpers/query.rs` (+1 -1) 📝 `bin/core/src/helpers/update.rs` (+29 -2) 📝 `bin/core/src/listener/resources.rs` (+3 -2) 📝 `bin/core/src/monitor/helpers.rs` (+1 -0) 📝 `bin/core/src/monitor/mod.rs` (+17 -3) _...and 70 more files_ </details> ### 📄 Description - **Keep images/containers up to date automatically.** There are 3 levels depending on how far you want to go for the automation: - **Manual**: (default) - Log in and use the "Pull" execution on Stacks / Deployments to pull latest image, and notify in the UI of an available update. - **Poll for Update**: Pull in the background (default 5 min, use KOMODO_RESOURCE_POLL_INTERVAL to change). If there is an update available, the user will be notified, and an alert will be sent out. It will not deploy the update, preferring to just let the user know for them to do the update at their convenience. - **Auto Update**: Whenever an update is found, it will skip sending an alert, and just go right ahead and redeploy. With this option selected, your running images will be kept up to date totally hands free. Note that it will only check for newer image at the same tag. If you use a versioned tag, it will not change the tag to a newer one. The intention is that users use latest tags. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-10-31 15:19:06 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
 question
security
seen 👀
setup
thinking 🤔
ui
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#705
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?