Repository navigation
docs(5dive-cli): ask for a key with several parts in one secret gate (DIVE-7184) - #43
Merged
Merged
Conversation
…(DIVE-7184) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: dev <oa-5795f249f0bf@openagent.5dive.ai>
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.
The 5dive-cli skill's secret section now names the one-gate form for a key with several parts (X's four values, AWS, OAuth client id + secret):
--secret-key=A,B,C,D, one link with a box per part. It also says a second secrettask needon the same row is refused.Pairs with 5dive-ai/5dive#1465, which adds the form and the refusal. On a CLI before that release the comma form is refused at filing with "invalid --secret-key", so nothing breaks; the agent files the parts one by one as before.
🤖 Generated with Claude Code