Add DeployHQ to Tools (Git-driven deploys for non-Kubernetes targets)#73
Open
facundofarias wants to merge 1 commit into
Open
Add DeployHQ to Tools (Git-driven deploys for non-Kubernetes targets)#73facundofarias wants to merge 1 commit into
facundofarias wants to merge 1 commit into
Conversation
|
How does this adhere to the GitOps Principles? They are:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds DeployHQ to
## Tools.DeployHQ applies the GitOps principle — Git as the source of truth, push-to-deploy, full history and rollback — to deployment targets the existing entries don't cover: VPS and bare metal via SSH/SFTP, static sites to S3, and PaaS targets. Commits to GitHub, GitLab, or Bitbucket trigger declarative build-and-deploy pipelines with zero-downtime deploys and one-click rollback to any prior commit.
The list is Kubernetes-heavy by design, so this is explicitly the non-K8s case. If that's outside the list's intended scope, please close — I won't push back. The entry is slotted alphabetically between CloudBees Rollout and Flux.