Lewis Rodgers lewisrodgers

Some starter files to get up and running with App Engine and Flask.

Place home.html in a folder called templates.

The folder structure will look something like this:

— root/
  — lib/
 — templates/

Prerequisites

For a more detailed version of the steps below visit: https://developers.google.com/admin-sdk/directory/v1/guides/delegation

Enable the necessary APIs (calendar, drive, gmail, etc.) in Cloud Console
Create a service account, download the json key file, and enable domain wide delegation (DwD)
Determine the required scopes (calendar readonly, drive read/write, etc.)
In the G Suite console, an admin authorizes the service account (client ID) with the specified scopes
The admin also identifies an account — with proper admin privileges — that the service account will impersonate (when you want to access user's data without manual authorization from the user)

Google Cloud Platform certification exam resources

A collection of case studies, white papers, articles, books, and other resources to help prepare you for a Google Cloud Platform certification or two.

Cloud Certification Forum on Google Cloud Connect
Deconstructing a Customer Case: Cloud Architect Exam - Customer case analysis on JencoMart, MountKirk Games, Dress4Win and TerramEarth
Cloud Architect Practice Exam
Qwiklabs GCP Quest

If you interested in a particular topic, a good place to start is the Tutorials and Solutions section of cloud.google.com. Search by keyword or browse around. Otherwise, I've currated some of the articles I think would be helpful and added t

Deploying Cloud Functions to schedule a Python Dataflow pipeline.

Use this as a guide. But instead of using the java runtime, we'll use python.

The setup can be accomplish with virtualenv to create an isolated environment.

The project folder structure will look like this:

cloudfunction/

	import time


	# Cloud Pub/Sub ###########################
	from google.cloud import pubsub

	client = pubsub.PublisherClient()
	topic = client.topic_path(PROJECT_ID, TOPIC_NAME)

	def send_to_pubsub(message, data):

	#!/bin/bash

	# This script is designed to update and publish a chrome extension
	# that already exists in the Chrome Web Store. It also depends on
	# OAuth 2.0 credentials and a refresh token.

	# Required arguments
	# ==================
	# There are 2 actions you can perform:
	# 1. Update - upload a chrome extension to the Chrome Web Store

	#!/bin/bash

	# This script is used to update a chrome extension that's already
	# been uploaded to the Chrome Web Store. You'll need to know the
	# chrome extension's ID that you want to update.
	# To find the app ID see: https://developer.chrome.com/webstore/publish#get-the-app-id
	#
	# usage:
	# ./chrome-web-store-api-update-utility.sh $APP_ID

	#!/bin/bash

	# This script generates a `tokens.json` file.
	#
	# example:
	# {
	# "access_token" : "ya29.Glst...",
	# "expires_in" : 3600,
	# "refresh_token" : "1/dd3t...",
	# "token_type" : "Bearer"

	# Possible versioning stratgy.
	# Only integers are allowed with the `version` property of the manifest.json.
	script:
	- GIT_HASH=$(git rev-parse --short HEAD)
	- jq ".version_name = \"build-$GIT_HASH\"" manifest.json \| spong manifest.json

	pipelines:
	branches:
	develop:
	- step:
	name: Update
	script:
	- apt-get update
	- apt-get -y install jq zip
	- FILE_NAME=crx.zip
	- zip -r $FILE_NAME ./app