feat: add hosts and postures endpoints with CRUD operations

[jaxxstorm]

Important

Add /hosts and /postures endpoints with CRUD operations and default posture handling in main.go, hosts.go, and postures.go.

• Behavior:
  • Adds /hosts and /postures endpoints in main.go for managing hosts and postures.
  • Supports CRUD operations for hosts and postures, including special handling for default postures.
• Hosts:
  • Implements RegisterRoutes in hosts.go to handle /hosts endpoints.
  • Provides functions for listing, creating, updating, and deleting hosts.
• Postures:
  • Implements RegisterRoutes in postures.go to handle /postures endpoints.
  • Provides functions for listing, creating, updating, and deleting postures, with special routes for default postures.

^{This description was created by for cb39868. It will automatically update as commits are pushed.}

[jaxxstorm]

Fixes #6
Fixes #7

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to cb39868 in 40 seconds

More details

• Looked at 617 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. pkg/acl/hosts/hosts.go:42

• Draft comment:
  Consider using a URL parameter for the host name in the DELETE /hosts endpoint instead of expecting a JSON body. This aligns with RESTful conventions and is more consistent with the GET /hosts/:name endpoint.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  This is a reasonable suggestion about API design and consistency. The code would be more RESTful and consistent if DELETE used the same URL parameter pattern as GET. However, both approaches are valid and commonly used. The current implementation works fine, and changing it would be a style preference rather than fixing a clear bug or issue.
  The current implementation with JSON body is also valid and has advantages - it's more extensible if more fields need to be added later, and some argue it's more explicit. The change would be purely stylistic.
  While both approaches are valid, consistency within the same API is valuable for developers using the API. The suggestion would improve the API's coherence.
  While this is a reasonable suggestion for improving API consistency, it's more of a style preference than a critical issue. The current implementation is valid and functional.

Workflow ID: wflow_Qbo8sOH3KrWaWoqg

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

Consider using a URL parameter for the posture name in the DELETE /postures endpoint instead of expecting a JSON body. This aligns with RESTful conventions and is more consistent with the GET /postures/:name endpoint.