Skip to content

Conversation

@westonplatter
Copy link
Member

@westonplatter westonplatter commented Apr 23, 2025

what

  • upgrade terraform docs to 0.20.0

references

Summary by CodeRabbit

  • Chores
    • Updated the terraform-docs tool and its configuration to version 0.20.0.

@westonplatter westonplatter requested a review from a team as a code owner April 23, 2025 23:09
@coderabbitai
Copy link

coderabbitai bot commented Apr 23, 2025

Walkthrough

The updates in this change focus on version bumps for the terraform-docs tool. Specifically, the configuration file .terraform-docs.yaml and the package manager configuration aqua.yaml both update their references from version 0.19.0 to 0.20.0. No other configuration settings, formatting, or package versions are modified.

Changes

File(s) Summary of Changes
.terraform-docs.yaml Updated terraform-docs configuration version from 0.19.0 to 0.20.0.
aqua.yaml Updated terraform-docs/terraform-docs package version from v0.19.0 to v0.20.0.

Poem

🎉
A version bump, a tiny leap,
From nineteen to twenty, our docs now keep.
Smooth and simple, the update flows,
As terraform-docs in new clothes goes.
With numbers changed, the future’s bright—
All’s in sync, and all’s just right!
🚀


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0aa8fc0 and ac19473.

📒 Files selected for processing (2)
  • .terraform-docs.yaml (1 hunks)
  • aqua.yaml (1 hunks)
🔇 Additional comments (2)
.terraform-docs.yaml (1)

1-1: Version bump to terraform-docs v0.20.0
The configuration now targets terraform-docs 0.20.0 as intended. This aligns with the PR objective, and no additional adjustments are needed here.

aqua.yaml (1)

13-13: Upgrade aqua package to terraform-docs v0.20.0
The Aqua manifest has been updated to use terraform-docs v0.20.0, matching the .terraform-docs.yaml change. All set!


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Member

@Gowiem Gowiem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@gberenice gberenice merged commit 475707f into main Apr 24, 2025
2 checks passed
@gberenice gberenice deleted the feat/upgrade-tfdocs branch April 24, 2025 07:29
gberenice pushed a commit that referenced this pull request Apr 24, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.5.0](v0.4.0...v0.5.0)
(2025-04-24)


### Features

* upgrade terraform docs
([#23](#23))
([475707f](475707f))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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

Successfully merging this pull request may close these issues.

5 participants