Including functionaity for service accounts #91
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
The previous version only supported the ability to authenticate through developer accounts. Changes are made to support usage of service accounts as a means of authentication.
Context: From a company perspective using service accounts are more desirable than using developer accounts. Now, the current support for service accounts requires sending in a valid json file path, which for certain companies can be a risky scenario if they are not able to encrypt it properly, hence using a json string containing contents is an easier fix for some companies which already encrypt such strings using tools like 1password.
Important: Requires this MR to be merged first.
QA steps
Closely related
googleads/google-ads-python#871