Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spike login should inform user to run spike init first if the system is not initialized. #37

Open
v0lkan opened this issue Nov 16, 2024 · 0 comments
Labels
good first issue Good for newcomers

Comments

@v0lkan
Copy link
Contributor

v0lkan commented Nov 16, 2024

When you do a spike get w/o initialization you get a warning to run spike init.

However, that does not happen for spike login.

It should.

dump:

volkan@spike:~/.spike$ spike get /db
>>>>>>>>>>>>>>>Posting to https://localhost:8553/v1/init?action=check
{"time":"2024-11-15T18:09:12.541849955-08:00","level":"INFO","msg":"post","path":"https://localhost:8553/v1/init?action=check"}
Please initialize SPIKE with `spike init` first.
volkan@spike:~/.spike$ spike login
Enter admin password: 
{"time":"2024-11-15T18:09:28.127624512-08:00","level":"INFO","msg":"post","path":"https://localhost:8553/v1/login?action=admin-login"}
Failed to login:
login: I am having problem sending the request
unauthorized
volkan@spike:~/.spike$ 
@v0lkan v0lkan added the good first issue Good for newcomers label Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant