Skip to content
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

Fix update_hoc_map to use updated Google client API #16132

Merged
merged 2 commits into from Jun 29, 2017

Conversation

breville
Copy link
Member

With the update of google-api-client from 0.8.6 to 0.10.3 in #15995, we had to update this cronjob script to use the new API.

To make it work, I also updated our credential from a legacy PKCS #12 to the recommended JSON format. I created a Service Account with Editor permission, and we shared the FusionTables table in question with that account, giving it "can edit" permission.

With the update of google-api-client from 0.8.6 to 0.10.3, we had to update this cronjob script to use the new API.

To make it work, I also updated our credential from a legacy PKCS #12 to the recommended JSON format.  I created a Service Account with Editor permission, and we shared the FusionTables table in question with that account, giving it "can edit" permission.
@breville
Copy link
Member Author

I haven't fully tested this, particularly with chef credential integration, but I did manage to make a post from my local machine to the FusionTable. Since it can't really get more broken, merging now, and we'll see how it copes on production, where we have already attempted to add the appropriate credential which will apply in the same DTP as this change.

@breville breville merged commit 63811da into staging Jun 29, 2017
@breville breville deleted the fix-update-hoc-map branch June 29, 2017 01:19
@breville
Copy link
Member Author

Got this working with a couple touch-ups:
#16180
#16211

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants