-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
collecting property sets #1
Labels
Comments
Hi Thomas,
Thanks for sharing this. I actually had no idea about sets. It looks like
sets are incongruous with the fundamentals of how this was coded at the
moment. Specifically, not being able to add additional users. It gets a
bit messy with authentication and one of our requirements was to stay as
simple to implement as possible. I will continue to look at sets to see if
they extend functionality.
JR
On Aug 29, 2017 11:02 AM, "Thomas Korrison" <[email protected]> wrote:
Great work guys! saving me a tonne of hours already!
Just a thought, or feature request...any ideas on how to add support for
property sets, from google's documentation
<https://support.google.com/webmasters/answer/6338828?hl=en&ref_topic=4564315>
it seems that they can only have one owner and cannot be shared.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJuCuRQ5aB-z02Rl9Kbs2XipBAl7w6znks5sdCf5gaJpZM4PGFxY>
.
|
the "create_delegated" method in the ServiceAccountCredentials object might be of use... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Great work guys! saving me a tonne of hours already!
Just a thought, or feature request...any ideas on how to add support for property sets, from google's documentation it seems that they can only have one owner and cannot be shared.
The text was updated successfully, but these errors were encountered: