feat(cli-2): add dk namespace policy get/set + bump dakera-client 0.8→0.9#22
Merged
Conversation
- Add 'Getting Started' section with dk init wizard - Improve intro description: add context on what dk manages Co-Authored-By: Paperclip <noreply@paperclip.ing>
…→0.9 Closes CLI-2. Exposes the full memory lifecycle policy surface via the CLI so users don't need raw HTTP calls to configure COG-1 TTLs, COG-3 background consolidation, or SEC-5 per-namespace rate limiting. Changes: - New `dk namespace policy get <ns>` — prints current MemoryPolicy as table or JSON (TTLs, decay curves, spaced repetition, consolidation, rate limits, consolidated_count). - New `dk namespace policy set <ns> [flags]` — read-modify-write: fetches current policy, applies only the supplied flags, clears read-only consolidated_count, then PUTs the result. All COG-1/COG-3/SEC-5 fields are exposed as named flags (see --help). - Bumps dakera-client 0.8 → 0.9 to access get_memory_policy/set_memory_policy and the updated MemoryPolicy with SEC-5 rate-limiting fields. - Fixes ConsolidateRequest initializer (memory consolidate cmd) to include new optional config field added in dakera-client 0.9 (CE-6 CE-6). Co-Authored-By: Paperclip <noreply@paperclip.ing>
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
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
Closes CLI-2. Exposes the full memory lifecycle policy surface via the CLI — no more raw HTTP calls to configure COG-1 TTLs, COG-3 background consolidation, or SEC-5 per-namespace rate limiting.
New commands
Prints the current
MemoryPolicyfor a namespace (TTLs, decay curves, spaced repetition, consolidation settings, rate limits,consolidated_count) in table or JSON format.Read-modify-write: fetches the current policy, applies only the supplied flags, clears the read-only
consolidated_count, then PUTs the result. All fields from COG-1, COG-3, and SEC-5 are exposed as named flags. Run--helpfor the full list.Example:
Other changes
dakera-client 0.8 → 0.9to accessget_memory_policy/set_memory_policyand the updatedMemoryPolicystruct with SEC-5 rate-limiting fields.ConsolidateRequestinitializer in thememory consolidatecommand to include the new optionalconfigfield added in dakera-client 0.9 (CE-6).Tests
cargo check+cargo test: 27/27 pass, 0 warnings.🤖 Generated with Claude Code