fix: update code blocks with the actual syntax

[gberenice]

what

• Update versioning code blocks in "The Ultimate Terraform Versioning Guide"

why

• In modern TF (>1.7), required_providers should use the object form and include the source. Omitting the source makes TF assume hashicorp/<name> for backward-compatibility, but it's recommended to specify it explicitly. 
• The string shortcut (aws = "~> 5.81.0") is the pre-0.13 style. Today, the docs show the object form (aws = { source = "..."; version = "..." }) and call out the older style as legacy. 

references

• https://developer.hashicorp.com/terraform/language/providers/requirements

Summary by CodeRabbit

• Documentation
  • Updated blog post with improved Terraform provider declaration examples, demonstrating best practices for explicit provider source specification and version constraints.

[netlify]

✅ Deploy Preview for masterpoint ready!

Name	Link
🔨 Latest commit	7df052b
🔍 Latest deploy log	https://app.netlify.com/projects/masterpoint/deploys/691dee386a60e800089601bd
😎 Deploy Preview	https://deploy-preview-90--masterpoint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 29 Accessibility: 86 Best Practices: 92 SEO: 79 PWA: 70 View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

This PR updates the Terraform required_providers syntax in a blog post, converting two AWS provider declarations from shorthand string format to full provider objects with explicit source specifications. The changes demonstrate updated provider configuration best practices without altering functional behavior.

Changes

Cohort / File(s)	Summary
Blog post documentation updates content/blog/2025-09-15-ultimate-terraform-versioning-guide.md	Rewrites two Terraform required_providers entries from shorthand strings to full provider objects, adding explicit source = "hashicorp/aws" specifications alongside version constraints

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Simple documentation/example syntax update with no logic changes
• Single file modification with straightforward, repetitive edits

Possibly related PRs

• feat: adds TF versioning blog post content #79 — Also modifies the same blog post file covering Terraform versioning practices

Suggested reviewers

• oycyc

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: update code blocks with the actual syntax' accurately describes the main change: updating Terraform code examples to use correct/modern syntax (object form with explicit source specification).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/version-guide-update-syntax

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ab83aad and 7df052b.

📒 Files selected for processing (1)

• content/blog/2025-09-15-ultimate-terraform-versioning-guide.md (2 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

content/**/*.md

📄 CodeRabbit inference engine (CLAUDE.md)

content/**/*.md: Place all site content in Markdown files under /content/
Use absolute URLs in content (paths should start with "/", e.g., /blog/ not blog/)
Reference images in content using the /img/ path (which maps to /static/img/)
Use front matter draft: true to hide in-progress content from production
Use provided Hugo shortcodes (button, buttonout, form, testimonials, faqs, team, services, process, supports, client-logos) in content instead of duplicating HTML

Files:

• content/blog/2025-09-15-ultimate-terraform-versioning-guide.md

content/blog/[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]-*.md

📄 CodeRabbit inference engine (CLAUDE.md)

Blog post files must use date-prefixed naming: YYYY-MM-DD-title.md under content/blog/

Files:

• content/blog/2025-09-15-ultimate-terraform-versioning-guide.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Redirect rules - masterpoint
• GitHub Check: Header rules - masterpoint
• GitHub Check: Pages changed - masterpoint

🔇 Additional comments (2)

content/blog/2025-09-15-ultimate-terraform-versioning-guide.md (2)

107-110: Child module provider syntax update is correct and consistent with guidance.

The conversion to explicit object form with source specification is accurate for modern Terraform (1.7+). The ">= 5.0.0" minimum version constraint appropriately aligns with the child module philosophy described in the preceding text—allowing consuming root modules flexibility to choose newer versions.

---

132-135: Root module provider syntax update is correct and consistent with guidance.

The object form with explicit source specification and pessimistic constraint "~> 5.81.0" correctly reflects the root module best practice described in the section. This ensures patch-level updates while preventing unexpected minor/major version surprises, as intended by your guidance.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[oycyc]

Small comment!

[oycyc]

We should use this! Helps with SEO indexing, as they like to see updated content
# date_modified: 2025-xx-xx Be sure to use this if you've updated the post as this helps with SEO and index freshness

[Gowiem]

Great follow up -- Thanks @gberenice 💯 !!

[westonplatter]

This looks good to me!