Steve Coffman StevenACoffman

How to use Python3 Type Hints in AWS Lambda

TL;DR

Static Type Checkers help you find simple (but subtle) bugs in your Python code. Check out lambda_types.py and incrementally improve your code base and development/debugging experience with type hints.

Your Lambda Function code will go from this:

Enter this in the search box along with your search terms:

Get all gists from the user santisbon.
user:santisbon

Find all gists with a .yml extension.
extension:yml

Find all gists with HTML files.
language:html

	package main

	import (
	"io/ioutil"
	"log"
	"net/http"
	"net/url"
	"strings"

	"crypto/rsa"

	apiVersion: v1
	data:
	config.yml: \|-
	global:


	# The directory from which notification templates are read.
	templates:
	- '/etc/alertmanager/template/*.tmpl'

	#!/bin/bash

	DAYS=("2017-12-06" "2017-12-07" "2017-12-08")
	for DAY in "${DAYS[@]}"; do
	#Super shitty pipefest because of grep matched groups sadness
	LINKS=($(curl https://kccncna17.sched.com/${DAY}/overview \| grep -oEi "f='(.*)' cl" \| cut -d\' -f 2 \| tr '\n' ' '))
	for LINK in "${LINKS[@]}"; do
	echo "Requesting https://kccncna17.sched.com/${LINK}"
	#Find file link on event page
	FILE_URL=$(curl -s https://kccncna17.sched.com${LINK} \| grep "file-uploaded" \| cut -d\" -f 4)

	/*
	Copyright (c) 2017, Sky UK Ltd All rights reserved.

	Redistribution and use in source and binary forms, with or without modification, are permitted provided
	that the following conditions are met:

	Redistributions of source code must retain the above copyright notice, this list of conditions and the
	following disclaimer.

	Redistributions in binary form must reproduce the above copyright notice, this list of conditions and

	from __future__ import print_function
	import json, urllib, urllib2

	def send_slack(message):
	"""
	Send Slack Message to Deployments Channel
	"""
	slack_token = ''
	slack_channel = ''
	slack_user = 'Deployment Bot'

	# Generate a new pgp key: (better to use gpg2 instead of gpg in all below commands)
	gpg --gen-key
	# maybe you need some random work in your OS to generate a key. so run this command: `find ./* /home/username -type d \| xargs grep some_random_string > /dev/null`

	# check current keys:
	gpg --list-secret-keys --keyid-format LONG

	# See your gpg public key:
	gpg --armor --export YOUR_KEY_ID
	# YOUR_KEY_ID is the hash in front of `sec` in previous command. (for example sec 4096R/234FAA343232333 => key id is: 234FAA343232333)

	const obj = { a: 1, c: 3, b: 2 }

	// Map from object.
	const myMap = new Map(Object.entries(obj))

	// Map to Object.
	// NOTE: Keys will be cast to strings by `.toString`, so any "complex" key like for example `[1, 2]` will become `1,2`
	const newObj = [...myMap.entries()]
	.reduce((acc, [key, value]) => (Object.assign(acc, { [key]: value })), {})

	--- PSQL queries which also duplicated from https://github.com/anvk/AwesomePSQLList/blob/master/README.md
	--- some of them taken from https://www.slideshare.net/alexeylesovsky/deep-dive-into-postgresql-statistics-54594192

	-- I'm not an expert in PSQL. Just a developer who is trying to accumulate useful stat queries which could potentially explain problems in your Postgres DB.

	------------
	-- Basics --
	------------

	-- Get indexes of tables