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

bug: CLI not working #6981

Open
2 of 3 tasks
BRAVO68WEB opened this issue Jan 25, 2025 · 3 comments
Open
2 of 3 tasks

bug: CLI not working #6981

BRAVO68WEB opened this issue Jan 25, 2025 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@BRAVO68WEB
Copy link

Describe the bug

Unable to run DB alterations using db alterations

Expected behavior

Perform DB alterations using CLI

How to reproduce?

  • run the following command
npx @logto/cli db alteration deploy

Context

  • Logto Cloud
  • Self-hosted, Logto version =
    • Container (Docker image)

Screenshots

Image

@BRAVO68WEB BRAVO68WEB added the bug Something isn't working label Jan 25, 2025
@Petteroe
Copy link

I have the same issue. I have tried with Node versions 20 (AWS ECS deploy), and 20 and 22 locally. I have tried with Logto docker images latest and 1.22.
I cannot even run the CLI locally with basic "logto --help", because I get the same exception as above.

@BRAVO68WEB
Copy link
Author

BRAVO68WEB commented Jan 25, 2025 via email

@BRAVO68WEB BRAVO68WEB changed the title bug: bug: CLI not working Jan 25, 2025
@darcyYe
Copy link
Contributor

darcyYe commented Jan 26, 2025

Could you try using logto db alteration deploy {version} for applying DB alteration?
We've refactored some parts of @logto/cli but haven't released a new version yet, and your error might be related to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

3 participants