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

Steampipe creates .pipes folder in $HOME, not respecting install dir parameters #4402

Open
massynmantel opened this issue Oct 3, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@massynmantel
Copy link

Describe the bug
Installing Steampipe in a different folder using the --install-dir and STEAMPIPE_INSTALL_DIR options, however Steampipe is still trying to create a folder called .pipes in the HOME folder.

Steampipe version (steampipe -v)
Example: v0.24.2

To reproduce
Change the $HOME folder to something like a read-only folder. Run steampipe with the --install-dir folder, pointing to any other folder.

Expected behavior
Steampipe should be using the provided parameter, and not continue to use the $HOME folder.

Additional context
None

@massynmantel massynmantel added the bug Something isn't working label Oct 3, 2024
@pskrbasu
Copy link
Contributor

pskrbasu commented Oct 3, 2024

@massynmantel Thanks for bringing this to our attention. We will take a look into this.

@albertopasqualetto
Copy link

I don't understand if, based on migrateDefaultTokenFile, the token directory should be ~/.steampipe/internal or ~/.pipes/internal.

Since in other functions it seems to be the first, but in the function's comment, it seems to be the latter.

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

No branches or pull requests

3 participants