Hi, I am from the Akkio team. I am currently trying to use the google analytics tap for multiple users to ad-hoc retrieve data from google analytics on our platform. One issue that we ran into is that the field

reports

expects a file path. It expects that we save a reports.json file for each import in our /meltano directory. This complicates our use case since we have many users. We would have to save various reports.json files, map to correct users, as well as maintain accuracy. Based on the tap-google-analytics repo, it was a small function change to be able to directly pass the reports json as a config that we can save with all other user configs. My original thought was to add this functionality and then open out a PR against the tap-ga4 repo to merge this as an update. This is the repo that I created as a fork from google analytics tap. We wanted to consult someone from Meltano to see if there was a better or more suggested way to deal with this issue of managing configurations when config files are expected to be saved in the meltano directory for multiple users.

@nidhi_kakulawaram this seems like a great feature to add! Many users only need their own single set of reports but for your use cases it makes total sense that you'd need a way to inject them without persisting each one to a file. If you create a PR I can help review it 😄

Great to hear that I'm on the right track with my approach! Here's a PR I opened: https://github.com/MeltanoLabs/tap-google-analytics/pull/151 Would appreciate a review when you have a sec! 😊