🔧 Update add-on paths, map directly to /config

[frenck]

Proposed Changes

SSIA, need an update to the add-ons validator.

Summary by CodeRabbit

• New Features

  • Enhanced clarity in resource configuration with explicit definitions for resource types and permissions in the map configuration.
  • Updated symbolic link for user configuration from "/homeassistant" to "/config".

• Bug Fixes

  • Removed unnecessary variable declaration to simplify script management.

• Refactor

  • Streamlined configuration entries for better readability and maintenance.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve updates to the configuration and script files within the project. The vscode/config.yaml file's map configuration has been restructured to provide explicit definitions for resource types, including a new path for homeassistant_config. Additionally, a variable declaration was removed from the finish script in the s6-rc.d/code-server directory, simplifying variable management. Lastly, the symbolic link target in the init-user/run script was updated to link directly to /config, replacing the previous link to /homeassistant.

Changes

File Path	Change Summary
vscode/config.yaml	Restructured map configuration for explicit resource definitions, added path for homeassistant_config.
vscode/rootfs/etc/s6-overlay/s6-rc.d/code-server/finish	Removed declaration of variable exit_code, simplifying variable management.
vscode/rootfs/etc/s6-overlay/s6-rc.d/init-user/run	Updated symbolic link target from "/homeassistant" to "/config" in the user's home directory.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Config
    participant Script

    User->>Script: Execute finish script
    Script->>Script: Read exit_code_container and exit_code_service
    Script->>Config: Access updated configuration
    Config-->>Script: Provide new resource definitions
    Script->>User: Complete execution

Loading

Poem

🐇 In the land of code where changes bloom,
A map was drawn to dispel the gloom.
Links now point where they should go,
Simplified scripts, a smoother flow.
With each update, the bunnies cheer,
For clearer paths, we hold so dear! 🌼

---

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 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.