Is there a way to completely eliminate .meltano fo...
# best-practices
k
Is there a way to completely eliminate .meltano folder creation, logs and etc? We want to use meltano to just run tap-target pipelines via command line. Our file system is read only and hence, getting errors during creation of .meltano folder
a
I imagine there could be some OS-level workaround but no, I am not aware of a way to invoke meltano without a writeable
.meltano
folder.
Are there any (perhaps ephemeral) directories that you'd have write access on? Perhaps a symlink solution could provide a workaround if so? You could safely ignore the files written there but Meltano would still need access to write them.
k
I am using MWAA. where, S3 is directly mounted. I think I can probably use /tmp folder. It would have been awesome if meltano can create temporary folders in \tmp folder and clean up right after execution.
I did go through the code and have a forked version which I modified and does that. Basically, writing to temporary folder and cleaning up right after ELT execution is complete. But, that forked version of code is a very old version. Just wanted to know if this has been possible with the latest version.
the hacks I did, its bad. I am sure(😅). But, it works. So, didn't touch it in a while
a
@kk - Thanks for sharing more info on the use case and your workaround. I don't see any reason why we couldn't make the location of
.meltano
configurable so it could live at
~/.meltano
or
/tmp/.meltano
(for instance). We'd welcome a feature request as an Issue, and PR too if you felt inspired. 🙂
k
So, I created a issue here- https://github.com/meltano/sdk/issues/907. I'll work on this one. Hopefully, it will be a moderate difficulty ride 😄
a
Thanks @kk!