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

Add questions on ArgoCD

Browse Source 
As well as on other topics.
This commit is contained in:
abregman
2022-09-14 21:39:47 +03:00
parent 3d129216e0
commit e56bf576df
7 changed files with 243 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
topics/terraform/README.md
View File

@@ -276,15 +276,21 @@ resource "aws_instance" "tf_aws_instance" {
<details>
<summary>How do you test a terraform module?</summary><br><b>
Many examples are acceptable, but the most common answer would likely to be using the tool <code>terratest</code>, and to test that a module can be initialized, can create resources, and can destroy those resources cleanly.
There are multiple answers, but the most common answer would likely to be using the tool <code>terratest</code>, and to test that a module can be initialized, can create resources, and can destroy those resources cleanly.
</b></details>
<details>
<summary>Where can you obtain Terraform modules?<summary><br><b>
<summary>Where can you obtain Terraform modules?</summary><br><b>
Terraform modules can be found at the [Terrafrom registry](https://registry.terraform.io/browse/modules)
</b></details>
<details>
<summary>There's a discussion in your team whether to store modules in one centralized location/repository or have them in each of the projects/repositories where they are used. What's your take on that?</summary><br><b>
You might have a different opinion but my personal take on that, is to keep modules in one centralized repository as any maintenance or updates to the module you need to perform, are done in one place instead of multiple times in different repositories.
</b></details>
### Variables
<details>