Support a true GitOps workflow

Open
#264 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, go, kubernetes
Domain
ci-cd, devops, infrastructure

Research direction

Start by tracing the existing draft create, draft setup-gh, and draft generate-workflow entry points across the az-extension, oss draft, and vscode surfaces. Compare their current push-based behavior with the requested repository structure, ArgoCD bootstrap and image-update flow; done means the three-step pull-based workflow is defined and supported consistently across the affected surfaces.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
As a user, I'd like to be able to utilize true pull-based GitOps workflows for Day 1/2+ operations after getting started. The existing push-based model does not scale as the number of applications, teams, and clusters grow.

Mention what platform you want to support the new feature
Has implications possibly across all of: az-extension, oss draft, and vscode.

Describe the solution you'd like

  1. draft create provisions a GitOps-friendly/planned repo structure and optionally wraps the structure in ArgoCD application(Set).
  2. draft setup-gh or likely alternative command bootstraps the cluster with ArgoCD agent sync'ed to the repo specified
  3. draft generate-workflow still sets up the pipeline to build the container image, but it does not authenticate/kubectl apply push down to the cluster. The ArgoCD agent in the previous step will automatically install the newly created container image after it is merged into the proper git directory as specified previously.

Describe alternatives you've considered
https://github.com/gitops-bridge-dev/gitops-bridge-argocd-control-plane-template
https://github.com/argoproj-labs/argocd-autopilot
https://github.com/alexellis/arkade?tab=readme-ov-file#catalog-of-clis -- ArgoCD

Dominant language
Go
Stars
644
Forks
74
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/draft

All issues in Azure/draft

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.