fix vendor pull error message

[samtholiya]

what

• New error message for vendor pull when config does not exist
  

why

• Old error message was not helpful
  

references

• https://linear.app/cloudposse/issue/DEV-2931/atmos-vendor-pull-prints-unhelpful-error-for-non-existant

Summary by CodeRabbit

• New Features

  • Added a new test case for the "atmos vendor pull" command.

• Bug Fixes

  • Improved error messaging for vendor configuration, providing clearer guidance when vendoring is not set up.

• Documentation

  • Enhanced error message includes a link to vendoring setup documentation.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request focuses on enhancing error handling in the atmos vendor pull command when a vendor configuration is missing. The changes improve the specificity of the error messages returned to users, providing clearer guidance and including a link to the documentation for setting up vendoring. Additionally, a new test case has been added to ensure the correctness of the updated error messaging behavior.

Changes

File	Change Summary
internal/exec/vendor_utils.go	Enhanced error handling in ReadAndProcessVendorConfigFile to provide specific error messages for missing configurations and permission issues.
tests/test-cases/vendor-test.yaml	Added a new test case named "atmos vendor pull" to verify the improved error messaging for the command.

Assessment against linked issues

Objective	Addressed	Explanation
Improve error message for non-existent vendor configuration [DEV-2931]	✅

Possibly related PRs

• Fix vendor pull directory creation issue #782: Similar modifications to error handling in vendor_utils.go.

Suggested labels

patch, minor

Suggested reviewers

• kevcube
• nitrocode

---

📜 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 c49448d and 719dee3.

📒 Files selected for processing (1)

• tests/test-cases/vendor-test.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• tests/test-cases/vendor-test.yaml

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Acceptance Tests (windows-latest, windows)
• GitHub Check: Summary

---

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

tests/test-cases/vendor-test.yaml (1)

4-4: Consider adding a test description.

Adding a brief description would help other developers understand the purpose of this test case.

-    description: ""
+    description: "Validates error message when vendoring is not configured"

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4799f28 and 2d58541.

📒 Files selected for processing (2)

• internal/exec/vendor_utils.go (1 hunks)
• tests/test-cases/vendor-test.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: Acceptance Tests (macos-latest, macos)
• GitHub Check: Acceptance Tests (windows-latest, windows)
• GitHub Check: Acceptance Tests (ubuntu-latest, linux)
• GitHub Check: [localstack] demo-localstack
• GitHub Check: Summary

🔇 Additional comments (2)

internal/exec/vendor_utils.go (1)

184-184: Great improvement to the error message!

The new error message is clear, actionable, and includes a helpful link to the documentation.

tests/test-cases/vendor-test.yaml (1)

2-13: Well-structured test case!

The test case properly validates both the error message and exit code for the vendor pull command.

[github-actions]

These changes were released in v1.146.3.