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

Error: during development, dashboard assets must be present when running powerpipe dashboard #524

Open
TheInverseKey opened this issue Oct 23, 2024 · 3 comments
Assignees

Comments

@TheInverseKey
Copy link

Powerpipe version (powerpipe -v)
v1.0.0

To reproduce

Follow the instructions from https://github.com/turbot/powerpipe/blob/develop/README.md
    instead of the installer scripts, I installed steampipe and powerpipe 
   ` the powerpipe -v works` and `powerpipe query run "select title from aws_account"`
Follow the instructions from https://powerpipe.io/docs#visualize-cloud-infrastructure
    When running powerpipe server, it prints `Error: during development, dashboard assets must be present when running powerpipe dashboard` and exits.
@pskrbasu pskrbasu self-assigned this Oct 23, 2024
@pskrbasu
Copy link
Collaborator

pskrbasu commented Oct 23, 2024

Powerpipe server requires dashboard assets to run. Dashboard assets are gzipped and built into the binary during release. When we run powerpipe server, they are unzipped and stored in $POWERPIPE_INSTALL_DIR/dashboard/assets dir. So if we have not downloaded the binary, they won't be available. Hence what you see here is expected.

The solution to this(building locally) is to run make dashboard_assets that builds the dashboard UI and extracts it to $POWERPIPE_INSTALL_DIR/dashboard/assets.

The only issue that needs fixing here is the error message, which should inform the users to run make dashboard_assets.

Thanks @TheInverseKey for raising this issue. I will get this done.

@TheInverseKey
Copy link
Author

@pskrbasu Is there an ETA on a fix for this?

@pskrbasu
Copy link
Collaborator

@TheInverseKey I will try and get the error message fixed next week. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants