Skip to content

Ansible definition contradictions #10570

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
FonzTech opened this issue Apr 7, 2025 · 1 comment
Open

Ansible definition contradictions #10570

FonzTech opened this issue Apr 7, 2025 · 1 comment

Comments

@FonzTech
Copy link

FonzTech commented Apr 7, 2025

Hi.

In Ansible exercises, it's told that:

True or False? Ansible uses declarative style to describe the expected end state
False. It uses a procedural style.

BUT in DevOps exercises, it's told that:

Explain Declarative and Procedural styles. The technologies you are familiar with (or using) are using procedural or declarative style?
Declarative Tools - Terraform, Puppet, CloudFormation, Ansible

Please, fix this.

Ansible clearly prioritizes declarative style!

Thanks.

@Manasa98-coder
Copy link

Ansible is primarily declarative in its approach to resource management (defining the what), even though its tasks are executed in a procedural sequence (the how of the playbook flow) and it allows for procedural overrides. Most practitioners and documentation emphasize its declarative nature. The DevOps exercise answer is the more widely accepted and useful description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants