Error storing deploy key: Invalid URL
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- graphql, typescript
- Domain
- authentication, cli
Research direction
Start by reproducing graph auth <Deploy_KEY> with a valid deploy key and trace the CLI authentication and key-storage entry points responsible for the prompt and Invalid URL error. Done means the provided key is accepted without an unnecessary prompt and authentication completes without the storage error.
Written by the indexing model from the issue text.
Description
Graph CLI Auth Issue
Description
When running the authentication step using the Graph CLI command:
graph auth <Deploy_KEY>
The CLI still prompts for the deploy key even though it is explicitly provided in the command. Additionally, it throws the following error:
Error: Error storing deploy key: Invalid URL
Even when I manually enter the deploy key when prompted, the error persists.
Steps to Reproduce
- Run
graph auth <Deploy_KEY>with a valid deploy key. - Observe that the CLI still asks for the deploy key.
- Enter the deploy key when prompted.
- See the error:
Error: Error storing deploy key: Invalid URL.
Expected Behavior
The Graph CLI should authenticate successfully without prompting for the deploy key if it is already provided in the command.
Actual Behavior
- CLI asks for the deploy key even when provided in the command.
- Throws
Invalid URLerror after entering the deploy key.
- Dominant language
- TypeScript
- Stars
- 186
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from graphprotocol/graph-client
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
graphprotocol/graph-client#1029 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphprotocol/graph-client#1031 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
graphprotocol/graph-client#1001 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
graphprotocol/graph-client#991 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
graphprotocol/graph-client#957 ·
All issues in graphprotocol/graph-client
Similar issues
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Fission-AI/OpenSpec#1986 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nestjs/docs.nestjs.com#3554 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
publicodes/publicodes#868 ·
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 78/100
EclipseFdn/open-vsx.org#13488 ·
Maintainers usually reply within 2 days