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

[massynmantel]

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

[pskrbasu]

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

[albertopasqualetto]

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.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.