I have been transitioning my homelab from UI defined to a written git resource sync and have come upon a missing value when defining a stack. Currently when a stack should be down or destroyed, there is no way to define this in the sync file.
Is it possible to get a value that defines if a stack should be deployed, down or even destroyed?
Originally created by @seraphblade2010 on GitHub (Nov 30, 2024).
Original GitHub issue: https://github.com/moghtech/komodo/issues/207
I have been transitioning my homelab from UI defined to a written git resource sync and have come upon a missing value when defining a stack. Currently when a stack should be down or destroyed, there is no way to define this in the sync file.
Is it possible to get a value that defines if a stack should be deployed, down or even destroyed?
Yeah I think you are right, the current solution of only deploy = true is not dynamic enough solution and I think a mistake to do it this way. I think it may be best to remove this deploy = true from the TOML and replace with something like:
ensure = "Running"
ensure = "Stopped"
It would be a breaking change to anyone using deploy = true though. It could also keep deploy = true just add stopped = true, but its a bit more awkward IMO, and less flexible.
<!-- gh-comment-id:2509022674 -->
@mbecker20 commented on GitHub (Nov 30, 2024):
Yeah I think you are right, the current solution of only `deploy = true` is not dynamic enough solution and I think a mistake to do it this way. I think it may be best to remove this `deploy = true` from the TOML and replace with something like:
- `ensure = "Running"`
- `ensure = "Stopped"`
It would be a breaking change to anyone using `deploy = true` though. It could also keep `deploy = true` just add `stopped = true`, but its a bit more awkward IMO, and less flexible.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @seraphblade2010 on GitHub (Nov 30, 2024).
Original GitHub issue: https://github.com/moghtech/komodo/issues/207
I have been transitioning my homelab from UI defined to a written git resource sync and have come upon a missing value when defining a stack. Currently when a stack should be down or destroyed, there is no way to define this in the sync file.
Is it possible to get a value that defines if a stack should be deployed, down or even destroyed?
@mbecker20 commented on GitHub (Nov 30, 2024):
Yeah I think you are right, the current solution of only
deploy = trueis not dynamic enough solution and I think a mistake to do it this way. I think it may be best to remove thisdeploy = truefrom the TOML and replace with something like:ensure = "Running"ensure = "Stopped"It would be a breaking change to anyone using
deploy = truethough. It could also keepdeploy = truejust addstopped = true, but its a bit more awkward IMO, and less flexible.