From 6cc9aeb225e553523ef4bf2c3b63e41c4a4212df Mon Sep 17 00:00:00 2001 From: Zach Aller Date: Mon, 21 Oct 2024 10:10:45 -0700 Subject: [PATCH] save Signed-off-by: Zach Aller --- docs/index.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/index.md b/docs/index.md index 4900bfc..30e53e5 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,6 +1,6 @@ # Welcome to GitOps Promotions -GitOps Promoter is a tool designed to facilitate environment promotion in a GitOps workflow. It automates the process of promoting changes from one environment to the next by leveraging Git operations. The tool ensures that your environments are always in sync with the desired state defined in your Git repository. +GitOps Promoter is a tool designed to facilitate environment promotion in a GitOps fashion. It automates the process of promoting changes from one environment to the next by leveraging Git operations. The tool can help ensures that your environments are always in sync with the desired state defined in your Git repository when used with a CD tool like ArogCD. ## Key Features @@ -8,10 +8,8 @@ GitOps Promoter is a tool designed to facilitate environment promotion in a GitO - **GitOps First**: Adheres to GitOps principles, ensuring that all changes are version-controlled. - **YAML Diff Detection**: Detects changes in YAML files to determine if a pull request is required. - **Integration with CI/CD**: Easily integrates with your existing CI/CD pipelines. -- **ArgoCD Integration**: Supports ArgoCD for managing Kubernetes resources. +- **ArgoCD Integration**: Supports ArgoCD when managing Kubernetes resources. -## Getting Started +## What is GitOps promotion. -To get started with GitOps Promoter, follow the [installation guide](installation.md) and the [basic usage instructions](getting-started.md). - -## Concepts of Promotion +GitOps promotion is the process of promoting changes across environments in a GitOps fashion. It involves using Git operations to manage the promotion of changes from one environment to the next. This ensures that all changes are version-controlled and that environments are always in sync with the desired state defined in your Git repository.