Added task for week-9 : Ansible#420
Conversation
WalkthroughThe update adds a detailed document outlining an "Ansible Automation Challenge" as part of the "90DaysOfDevOps" initiative. The document specifies five core tasks on various aspects of Ansible automation, including dynamic inventory configuration, Nginx playbook development, organizing playbooks with roles, secure data handling with Ansible Vault, and multi-tier deployment orchestration. A bonus task linking Terraform with Ansible for multi-environment setups is also provided. The submission instructions require documenting processes in a Changes
Suggested reviewers
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
2025/ansible/README.md (3)
32-34: Review Interview Question Punctuation.
Consider revising the interview question on line 34 to improve clarity. For example, adding a comma before “and” can help separate the two independent clauses:- - What challenges do dynamic inventory sources present and how can you mitigate them? + - What challenges do dynamic inventory sources present, and how can you mitigate them?🧰 Tools
🪛 LanguageTool
[uncategorized] ~34-~34: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ges do dynamic inventory sources present and how can you mitigate them? --- ## Tas...(COMMA_COMPOUND_SENTENCE_2)
143-147: Check Terminology Consistency.
Static analysis suggests reviewing the spelling of “multi-environment” on lines 143 and 147. If the project’s style guide prefers a single-word form (e.g., “multienvironment”), please update accordingly for consistency.🧰 Tools
🪛 LanguageTool
[misspelling] ~143-~143: This word is normally spelled as one.
Context: ...utputs integrate with Ansible to manage multi-environment deployments. Interview Questions: ...(EN_COMPOUNDS_MULTI_ENVIRONMENT)
[misspelling] ~147-~147: This word is normally spelled as one.
Context: ...challenges might you face when managing multi-environment configurations, and how do you overcome...(EN_COMPOUNDS_MULTI_ENVIRONMENT)
157-160: Suggest Specifying Code Block Language.
The fenced code block displaying the PR title (lines 158–160) currently does not specify a language. For better markdown linting and clarity, consider adding a language identifier (for example,text):- ``` - Week 9 Challenge - Ansible Automation Challenge - ``` + ```text + Week 9 Challenge - Ansible Automation Challenge + ```🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
159-159: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
2025/ansible/README.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
2025/ansible/README.md
[uncategorized] ~34-~34: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ges do dynamic inventory sources present and how can you mitigate them? --- ## Tas...
(COMMA_COMPOUND_SENTENCE_2)
[misspelling] ~143-~143: This word is normally spelled as one.
Context: ...utputs integrate with Ansible to manage multi-environment deployments. Interview Questions: ...
(EN_COMPOUNDS_MULTI_ENVIRONMENT)
[misspelling] ~147-~147: This word is normally spelled as one.
Context: ...challenges might you face when managing multi-environment configurations, and how do you overcome...
(EN_COMPOUNDS_MULTI_ENVIRONMENT)
🪛 markdownlint-cli2 (0.17.2)
2025/ansible/README.md
159-159: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
🔇 Additional comments (13)
2025/ansible/README.md (13)
1-3: Clear Introduction.
The title and opening paragraph set a strong context for the Ansible challenge and clearly introduce the theme for Week 9.
5-9: Clear Submission Instructions.
The guidelines for forking the repository, documenting the process insolution.md, and submitting the work are concise and easy to follow.
12-15: Well-Defined Task 1.
The description for installing Ansible and configuring a dynamic inventory is clear and contextualizes the production challenges effectively.
17-30: Detailed Steps for Task 1.
The step-by-step instructions covering installation, dynamic inventory configuration, connectivity testing, and documentation are thorough and actionable.
38-57: Comprehensive Task 2 for Nginx Setup.
The scenario and detailed steps for creating a robust playbook to install and configure Nginx—including using Jinja2 templates and implementing asynchronous execution with error handling—are very well articulated.
61-80: Well-Structured Task 3 on Playbook Organization.
The instructions for reorganizing playbooks into roles and managing advanced variable hierarchies are clear. The associated interview questions also prompt thoughtful discussion around scalability and collaboration.
83-102: Thorough Guidance for Ansible Vault Techniques.
The steps on encrypting sensitive data with Ansible Vault, integrating multiple encrypted files into playbooks, and verifying decryption are comprehensive and align well with real-world secure data management practices.
105-122: Effective Task 5: Multi-Tier Deployments.
The instructions for orchestrating a multi-tier application—including managing execution order and asynchronous tasks—are well-detailed and practical.
125-142: Clear Bonus Task Details.
The bonus task that integrates Terraform with Ansible is clearly outlined. The steps for provisioning with Terraform and configuring with Ansible are detailed; consider linking to Terraform documentation for further reading if desired.
161-171: Good PR Submission Guidelines.
The detailed steps for submitting the pull request, writing a descriptive PR description, and sharing your experience on LinkedIn are clear and encourage a comprehensive submission.
175-180: Useful Resource Section.
The curated TrainWithShubham resources provide valuable additional information that can aid in mastering Ansible and the associated concepts.
182-189: Comprehensive Additional Resources.
The links to the Ansible official documentation, modules documentation, Galaxy, and best practices offer a solid reference base.
190-194: Clear Final Instructions.
The concluding statement effectively summarizes the expectations and reinforces the challenge’s learning objectives.
2 participants
Summary by CodeRabbit