bugsink-cli 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 332213d0fe5dd0cffa80562ed080efcf15df8efb3a33d9efd6916bd5f3b86558
-  data.tar.gz: 752a775192b2bf8d719a1ac18b4916a8f619159b1dda6df6702a7e27adc8302a
+  metadata.gz: b89224f3bcb9eb69b009ea2f9ac7c4c95670130dc71aaa9bd001ef146f015b27
+  data.tar.gz: 051e79e4933a9150de8dd9383d8ccaa8550ba9ddc12424808c1dab60f61d8af6
 SHA512:
-  metadata.gz: 8be23b51ee505b803159e7aae993b91f091c21124980202f4a2e833f485b5faa3201ff41a7d3d74b499be1ddd7ef09de06c1a986238cf61a872869bae7a3bf1e
-  data.tar.gz: 5fcc6bcf7b826c2779879c4f9634393934d803c85951d9671e04d466aadbc31b35acab7bf800673135815d7977d92a6ed156cf3f40a42c4ff95cadc71e889724
+  metadata.gz: fd7e41a833fbbf36c268b731128a27335321496f2b90a6dec08e83e4788f244bea60ee1cac43117ecd3ab771d535af5f908f448402cd0ba663f8a32990ee1678
+  data.tar.gz: 8ca173e5b7280f9940dd57bcc157771f05319a1378c0a902ea94f9bade34f4bf0e9edd4d0952fb412f8892465c501179bbb22639b43f912c20dbc0cf18cfafeb

data/README.md

@@ -126,7 +126,7 @@ bugsink projects create '{
 bugsink projects update <id> '{"name":"New Name","alert_on_new_issue":false}'
 ```
 
-#### Issues (Read-Only)
+#### Issues
 
 ```bash
 # List issues for a project
@@ -137,9 +137,12 @@ bugsink issues list --project=<id> \
 
 # Get issue details
 bugsink issues get <uuid> [--json]
+
+# Resolve an issue
+bugsink issues resolve <uuid> [--json]
 ```
 
-**Note:** Issues are **read-only** via the API. You cannot update status, resolve, or add comments through the CLI.
+**Note:** The `resolve` command requires [bugsink-fork](https://github.com/landovsky/bugsink-fork), which adds the resolve API endpoint. Using it against upstream BugSink will return a 404 error.
 
 #### Events (Read-Only)
 
@@ -266,11 +269,11 @@ ee4f4572-0957-4346-b433-3c605acbfa2a
 
 - **Teams:** Create, Update
 - **Projects:** Create, Update
+- **Issues:** Resolve (requires [bugsink-fork](https://github.com/landovsky/bugsink-fork))
 - **Releases:** Create
 
 ### Read-Only Resources
 
-- **Issues:** Cannot update status, resolve, or add comments
 - **Events:** Created automatically via Sentry SDK ingestion only
 
 ### Not Supported
@@ -297,6 +300,9 @@ teams = response.data
 # Get project
 project = client.project_get(8)
 
+# Resolve an issue (requires bugsink-fork)
+issue = client.issue_resolve('issue-uuid')
+
 # Create release
 release = client.release_create(
   project_id: 8,

data/lib/bugsink/cli.rb

@@ -191,9 +191,18 @@ module Bugsink
         parse_format_options!(args[1..] || [])
         issue = @client.issue_get(uuid)
         output_single(issue, format: @options[:format])
+      when 'resolve'
+        uuid = args[0]
+        unless uuid
+          error('Issue UUID required')
+          exit 1
+        end
+        parse_format_options!(args[1..] || [])
+        issue = @client.issue_resolve(uuid)
+        output_single(issue, format: @options[:format])
+        success("Issue #{uuid} resolved")
       else
         error("Unknown issues action: #{action}")
-        info('Note: Issues are read-only. Write operations not available in API.')
         exit 1
       end
     end
@@ -391,7 +400,7 @@ module Bugsink
           config      - Configuration management
           teams       - Team operations
           projects    - Project operations
-          issues      - Issue operations (read-only)
+          issues      - Issue operations
           events      - Event operations (read-only)
           releases    - Release operations
 
@@ -413,6 +422,7 @@ module Bugsink
 
           bugsink issues list --project=<id>           List issues for project
           bugsink issues get <uuid>                    Get issue details
+          bugsink issues resolve <uuid>                Resolve an issue
 
           bugsink events list --issue=<uuid>           List events for issue
           bugsink events stacktrace <uuid>             Get formatted stacktrace
@@ -443,7 +453,7 @@ module Bugsink
           # Get stacktrace for an event
           bugsink events stacktrace <event-uuid>
 
-        Note: Issues and Events are READ-ONLY via the API. Write operations are not supported.
+        Note: Events are READ-ONLY via the API.
       HELP
     end
 
@@ -518,11 +528,12 @@ module Bugsink
         HELP
       when 'issues'
         puts <<~HELP
-          bugsink issues - Issue operations (READ-ONLY)
+          bugsink issues - Issue operations
 
           Actions:
             list --project=<id> [--sort=<field>] [--order=<asc|desc>]
             get <uuid>
+            resolve <uuid>
 
           Options:
             --project=<id>    Project ID (required for list)
@@ -532,8 +543,9 @@ module Bugsink
           Examples:
             bugsink issues list --project=8 --sort=last_seen --order=desc
             bugsink issues get <uuid> --json
+            bugsink issues resolve <uuid>
 
-          Note: Issues are READ-ONLY. No write operations available in API.
+          Note: Resolve returns 409 if the issue is already resolved.
         HELP
       when 'events'
         puts <<~HELP

data/lib/bugsink/client.rb

@@ -165,6 +165,12 @@ module Bugsink
       response.parsed_response
     end
 
+    def issue_resolve(uuid)
+      response = self.class.post("/api/canonical/0/issues/#{uuid}/resolve/")
+      check_response(response)
+      response.parsed_response
+    end
+
     # Events
     def events_list(issue_uuid:, order: 'desc', limit: 250, cursor: nil)
       query = {

data/lib/bugsink/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Bugsink
-  VERSION = '0.1.2'
+  VERSION = '0.1.3'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bugsink-cli
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - Tomas Kopernik