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

change Ansible from procedural to declarative (#319)

Browse Source
This commit is contained in:
Erik Zilinsky 2022-11-23 21:23:38 +01:00 committed by GitHub
parent fd88040f5e
commit 737c411ae8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
topics/devops/README.md
View File

@ -393,11 +393,11 @@ This situation might lead to bugs which hard to identify and reproduce.
<details>
<summary>Explain Declarative and Procedural styles. The technologies you are familiar with (or using) are using procedural or declarative style?</summary><br><b>
Declarative - You write code that specifies the desired end state
Declarative - You write code that specifies the desired end state<br><b>
Procedural - You describe the steps to get to the desired end state
Declarative Tools - Terraform, Puppet, CloudFormation
Procedural Tools - Ansible, Chef
Declarative Tools - Terraform, Puppet, CloudFormation, Ansible<br><b>
Procedural Tools - Chef
To better emphasize the difference, consider creating two virtual instances/servers.
In declarative style, you would specify two servers and the tool will figure out how to reach that state.