Added task for week-8 : Terraform#417
Added task for week-8 : Terraform#417LondheShubham153 merged 1 commit intoTrainWithShubham:masterfrom
Conversation
WalkthroughThe pull request adds a comprehensive guide for the "Week 8: Terraform (Infrastructure as Code) Challenge" within the 90DaysOfDevOps initiative. The document provides a series of tasks covering Terraform provisioning, state management, variables, modules, workspaces, resource lifecycle management, drift detection, and environment management. It also includes a bonus exercise for AWS infrastructure setup using Terraform and Ansible, detailed instructions for documenting the process, and guidelines for submission. No changes were made to the declarations of exported or public entities. Changes
Sequence Diagram(s)sequenceDiagram
participant P as Participant
participant G as Guide (README)
participant D as Documentation (solution.md)
participant R as Repository
P->>G: Read challenge guide
G-->>P: Provide detailed tasks & instructions
P->>P: Execute Terraform tasks (provisioning, state management, modules, etc.)
P->>D: Record steps and observations
P->>R: Fork repository & submit pull request
R-->>P: Confirm and merge submission
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 (6)
2025/terraform/README.md (6)
12-34: Comprehensive Task 1 Guidance
The detailed instructions for installing Terraform, initializing a project, and provisioning a basic resource are clear and sequential. Consider adding example configuration snippets or links to further reading to assist users who may be new to Terraform.
60-68: Compound Word Consistency
A static analysis hint noted on this segment suggests that the term “multi-environment” might need reviewing. Verify whether the compound should appear as “multienvironment” for consistency with your style guidelines.🧰 Tools
🪛 LanguageTool
[misspelling] ~68-~68: This word is normally spelled as one.
Context: ...n how these features enable dynamic and multi-environment deployments. Interview Questions: ...(EN_COMPOUNDS_MULTI_ENVIRONMENT)
136-154: Dynamic Pipeline Parameterization Task
This optional task introduces dynamic input parameters and conditional logic to adapt deployments per environment. The challenge adds depth; ensure that any provided code examples are well tested.
157-157: Markdown Styling: Bonus Task Header
There are extra spaces inside the bold emphasis markers in the bonus task title. Adjusting the header (e.g., removing trailing spaces) will ensure markdown lint compliance.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
157-157: Spaces inside emphasis markers
null(MD037, no-space-in-emphasis)
193-196: Specify Language for Fenced Code Block
The code block that shows the PR title does not specify a language. Adding a language tag (e.g.,text) will improve markdown compliance with linting rules.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
193-193: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
203-205: Consistency in Compound Terms
A static analysis hint flagged the compound term “multi-environment setups.” Please verify that the usage is consistent with your project's style guide—consider unifying the term to “multienvironment” if that aligns with your conventions.🧰 Tools
🪛 LanguageTool
[misspelling] ~204-~204: This word is normally spelled as one.
Context: ...agement, module usage, drift detection, multi-environment setups). - Use the hashtags: **#90Da...(EN_COMPOUNDS_MULTI_ENVIRONMENT)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
2025/terraform/README.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
2025/terraform/README.md
[misspelling] ~68-~68: This word is normally spelled as one.
Context: ...n how these features enable dynamic and multi-environment deployments. Interview Questions: ...
(EN_COMPOUNDS_MULTI_ENVIRONMENT)
[misspelling] ~204-~204: This word is normally spelled as one.
Context: ...agement, module usage, drift detection, multi-environment setups). - Use the hashtags: **#90Da...
(EN_COMPOUNDS_MULTI_ENVIRONMENT)
🪛 markdownlint-cli2 (0.17.2)
2025/terraform/README.md
157-157: Spaces inside emphasis markers
null
(MD037, no-space-in-emphasis)
193-193: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
🔇 Additional comments (11)
2025/terraform/README.md (11)
1-3: Clear and Structured Introduction
The title and opening lines clearly state the challenge focus and provide context for the tasks ahead.
4-11: Well-Defined Setup Instructions
The steps for forking the repository and documenting the work (i.e., creating asolution.mdfile) are clear and actionable.
35-54: Solid Remote State Management Instructions
The steps outlining the configuration of a remote backend and state locking are detailed and educational. The inclusion of interview questions reinforces the learning objectives.
55-74: Effective Task 3 Breakdown
The guidance on using variables, outputs, and workspaces is clear and practical.🧰 Tools
🪛 LanguageTool
[misspelling] ~68-~68: This word is normally spelled as one.
Context: ...n how these features enable dynamic and multi-environment deployments. Interview Questions: ...(EN_COMPOUNDS_MULTI_ENVIRONMENT)
76-94: Detailed Module Creation Task
Instructions for creating and using Terraform modules are comprehensive and well laid out. This section clearly emphasizes modular design and DRY principles.
95-114: Solid Guidance on Resource Dependencies and Lifecycles
The section effectively explains how to manage resource dependencies using thedepends_onmeta-argument and how to apply lifecycle configurations such ascreate_before_destroy.
116-134: Comprehensive Drift Detection Instructions
The steps to detect infrastructure drift viaterraform planand the follow-up strategies for change management are clearly outlined, reinforcing good infrastructure maintenance practices.
158-176: Robust Bonus Task Instructions
The bonus task provides a detailed, multi-step challenge integrating Terraform with Ansible for multi-environment AWS setups. The instructions are clear and encourage best practices in infrastructure automation.
185-207: Clear Submission and PR Guidelines
The “How to Submit” section clearly instructs users on pushing changes, creating pull requests, and even sharing their experience on LinkedIn, which fosters community engagement.🧰 Tools
🪛 LanguageTool
[misspelling] ~204-~204: This word is normally spelled as one.
Context: ...agement, module usage, drift detection, multi-environment setups). - Use the hashtags: **#90Da...(EN_COMPOUNDS_MULTI_ENVIRONMENT)
🪛 markdownlint-cli2 (0.17.2)
193-193: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
210-224: Valuable Resource Links
The section providing TrainWithShubham resources and additional links is well curated and offers useful references to users looking to deepen their understanding of Terraform.
228-229: Concluding Instructions
The final wrap-up sections succinctly remind users of the tasks and submission steps. This offers a clear conclusion to the guide.
2 participants
Summary by CodeRabbit