feat(raw): add storage management endpoints - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
raw storage-management get|updateso admins can script the newly released retention, gcQL exception-rule, and index-tier settings for logs, traces, events, APM measurements, and monitor issues.The commands use the existing gcsa-authenticated API transport, keep the broad HAR-generated registry intact, and expose the data type as
--data-type. README and the bundled Groundcover skill document the versioned full-replacement PUT contract, including preserving the complete custom-rule list.Validation
go test ./...go vet ./...gofmt -d internal/raw/command.go internal/raw/storage_management_commands.go internal/raw/runner_test.goraw storage-management get --data-type logsreturned the current settings fromapi.groundcover.comPost-Deploy Monitoring & Validation
No additional operational monitoring required. This is an additive client-only command registration with no deployed service path.
After the next CLI release, run
groundcover raw storage-management get --data-type logs; healthy output is a JSON object withdata_type,retention, andversion. HTTP 401 indicates credential/profile failure; HTTP 404/405 indicates endpoint or method drift. Roll back by reinstalling the previous CLI version. Validation window: first release smoke test. Owner: @Paymahn.