Repos-que-me-gustan/devops-exercises
1
0
Fork 0
Code Pull Requests Activity

Add a couple of questions

Browse Source
This commit is contained in:
abregman
2022-09-23 10:47:21 +03:00
parent b05e2e4109
commit df8b27522c
3 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
topics/devops/README.md
View File

@@ -436,6 +436,12 @@ Read more [here](https://about.gitlab.com/topics/gitops)
</b></details>
<details>
<summary>When a repository refereed to as "GitOps Repository" what does it means?</summary><br><b>
A repository that doesn't holds the application source code, but the configuration, infra, ... files that required to test and deploy the application.
</b></details>
<details>
<summary>What are some practical implementations or practices of GitOp?</summary><br><b>
@@ -448,7 +454,8 @@ Read more [here](https://about.gitlab.com/topics/gitops)
One might say we need more details as to what these configuration and infra files look like exactly and how complex the application and its CI/CD pipeline(s), but in general, most of the time you will want to put configuration and infra related files in their own separate repository and not in the repository of the application for multiple reasons:
* Every change submitted to the configuration, shouldn't trigger the CI/CD of the application, it should be testing out and applying the modified configuration
* Every change submitted to the configuration, shouldn't trigger the CI/CD of the application, it should be testing out and applying the modified configuration, not the application itself
* When you mix application code with conifguration and infra related files
</b></details>
#### SRE