Add support for helmfile version command

[samtholiya]

what

• Support for atmos helmfile version command

Currently:

After this pr:

why

We say atmos supports all native terraform commands, yet we do not support atmos helmfile version

references

issue: https://linear.app/cloudposse/issue/DEV-2844/atmos-helmfile-version-does-not-work
conversation: https://sweetops.slack.com/archives/D08447GN7JA/p1734006016227039?thread_ts=1734002589.248629&cid=D08447GN7JA

Summary by CodeRabbit

• New Features
  • Added support for the "version" command to display the helmfile version.
• Bug Fixes
  • Adjusted command-line interface behavior to ensure help is only triggered for commands other than "version".
• Documentation
  • Updated comments to reflect changes in command handling logic.
• Refactor
  • Streamlined the command-line argument processing for improved clarity.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes introduce a new handling pathway for the "version" subcommand in the ExecuteHelmfile function, allowing it to execute and return the helmfile version. Additionally, the processArgsAndFlags function in utils.go has been modified to ensure the help command is only triggered for commands other than "version." These adjustments enhance the command-line interface while preserving existing functionality and error handling.

Changes

File	Change Summary
internal/exec/helmfile.go	Added conditional branch in ExecuteHelmfile to handle "version" subcommand, executing helmfile version command.
internal/exec/utils.go	Modified processArgsAndFlags to adjust help flag logic, ensuring it only triggers for non-version commands; updated comments and reorganized code.

Assessment against linked issues

Objective	Addressed	Explanation
Support atmos helmfile version command (DEV-2844)	✅

Possibly related PRs

• Fix: condition to display help interactive menu #724: Modifies help command display logic, potentially interacting with the new "version" command handling.
• fix check the version if config broken #735: Introduces a function to check if the command is a version command, directly related to the changes made in the main PR.
• Fix helmfile demo #753: Updates ExecuteHelmfile for better handling of the KUBECONFIG environment variable, relevant to the changes in the main PR.

Suggested labels

minor

Suggested reviewers

• osterman
• aknysh
• joe-niland

---

📜 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 22c9b28 and 79495c9.

📒 Files selected for processing (2)

• internal/exec/helmfile.go (1 hunks)
• internal/exec/utils.go (1 hunks)

🔇 Additional comments (3)

internal/exec/helmfile.go (1)

57-59: LGTM! Clean implementation of version command support.

The implementation correctly handles the version subcommand by bypassing unnecessary stack configuration processing and directly executing the helmfile version command. This is an efficient approach since version information doesn't require stack context.

internal/exec/utils.go (2)

664-672: LGTM! Well-structured command handling logic.

The changes correctly differentiate between the version command and other commands, ensuring that:

1. Help is not triggered for the version command
2. Version command is handled appropriately
3. Other single-argument commands continue to show help

This implementation aligns well with the changes in helmfile.go.

---

674-676: LGTM! Clear variable declarations.

The global options handling variables are well-placed and clearly named, maintaining consistency with the existing codebase.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Experiment)
• @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 or @auto-summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @auto-title 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.

[aknysh]

thanks @samtholiya

[github-actions]

These changes were released in v1.126.0.