# GitOps

CI/CD workflow and tech stack.

![Gitflow](https://345815687-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9XSdc4ZLxsryuoSbTpFL%2Fuploads%2Fgit-blob-d4bc26b877f900bf8860bdd2e664816792f56890%2Fdev-sec-ops.drawio.svg?alt=media)

## Development

Main concepts of **Gitflow**:

* **main** branch will represent the currently developed release
* **main** branches will record the history of the project
* **feature** branch will contain the feature-developed changes. each feature will usually have a feature branch.
* **release** branch will represent the next phase of developed release before it is completed and merged to *master/main* branch

## Deployment

### Develop flow

> Microservices monorepo — automatically build and deploy latest changes to dev environment.

Every change that will be pushed to develop branch on the microservices repositories will be seen automatically deployed to the **dev environment**.

CI-CD based on dockers implementation description:

1. **build** (automatic) — Any commit to **develop/main/master branch** will trigger a **docker image build** that will be pushed to a docker container registry. If the change will be pushed to develop branch the docker image will be tagged with a tag **:latest**, otherwise, it will be tagged with the **:commit-id**
2. **deploy** (automatic)— The image tagged with **:latest** will be pulled automatically to the **dev environment.**

### Release flow

> Integration — deploy a release version to higher environments.

Every git tag that will be pushed to the **master/main branch** on the repository will be available to be deployed to the remote environments such as **stage** and **prod** by the following

CI-CD based on dockers implementation description:

1. **build** (automatic) — A **git tag** on the repository will represent all µService lib modules version together. *Images for these commit ids are already made and wait to be deployed on the container registry since their development passed on develop flow.* In kubernetes we use kustomize/helm representing these images with these commit-ids that will be built and pushed with the git tag to a remote **deploy registry.**
2. **deploy** (manual)— Images with the relevant commit ids will be pulled to the remote environment. In kubernetes we deploy by the kustomize/helm from the **deploy registry** to a remote environment.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://xmlking.gitbook.io/macos-setup/devops/development-workflow/gitops.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.