Dot-separated config keys are not nested in generated tap or target config
Problem to solve
CM Agencies often use role accounts to manage analytics on behalf of customers; requesting that separate service accounts be granted access to GA Reporting API adds friction. Singer's tap-google-analytics
currently supports authentication using oauth2
as well as using a service_account
for the auth_method
.
Target audience
Content marketing agencies using Meltano as part of their analytics ETL/ELT pipeline.
Further details
Primary goal: reduce friction in ingesting Google Analytics data on behalf of an agency's clients when the agency has already been granted access to those properties/views.
Proposal
I propose adding a config option (or a separate config for the existing extractor/tap) that supports using oauth2
credentials as the auth_method
.
Edited by Douwe Maan