| """ | |
| This is a small python script to clear up old gitlab build artifacts. | |
| There are 3 variables you should modify: | |
| * base_url: path to your gitlab | |
| * access_token: your personal access token to make gitlab api calls | |
| * delete_everything_older_than: configure the timedelta as you wish | |
| !!IMPORTANT!! | |
| By default this script does only make dry-runs and does not actually delete any files! |
| # watch the demo at https://youtu.be/cGUNf1FMNvI | |
| # | |
| # customize these variables | |
| # | |
| DEFAULT_PROFILE='default' | |
| DEFAULT_REGION='us-east-1' | |
| DEFAULT_OUTPUT='json' | |
| SSO_START_URL='https://your-sso.awsapps.com/start' | |
| SSO_REGION='us-east-1' | |
| SSO_ACCOUNT_ID='123456789012' |
############################################################################################################ ################## ############################# ################## #############################
This Gist collection contains all localstack related examples
################## ############################# ################## ############################# ############################################################################################################
Example of a bare-minimum terraform script to setup an API Gateway endpoint that takes records and puts them into an SQS queue.
Start by creating the SQS queue.
resource "aws_sqs_queue" "queue" {
| #!/usr/bin/env python | |
| import sys | |
| from ansible.parsing.vault import PromptVaultSecret, VaultLib | |
| from ruamel.yaml import YAML | |
| old_secret = PromptVaultSecret(prompt_formats=["Old password: "]) | |
| old_secret.load() | |
| new_secret = PromptVaultSecret(prompt_formats=["New password: "]) |
AWS API Gateway has the ability to pre-authenticate connections prior to launching the endpoint, by passing the authorizationToken to a Lambda function. There are clear benefits for simplifying end point security and also a reduction in duplicated code by utilising this feature. However I found the AWS examples were excessively complicated for what should be a very simple task.
So here's my example.
The main concern is that AWS Lambda authentication expects a very specific response and if that response is not given it will throw a 500 error with x-amzn-ErrorType: AuthorizerConfigurationException in the response header if the response object is not exactly as expected.
I personally use to handle the publishing part of my Lambdas, but I'll include an image of the API Gateway config.
These are instructions for standing up a Kubernetes cluster with Raspberry Pis with the current Hypriot (1.9.0), with K8S v1.10.5
Thanks to https://gist.github.com/alexellis/fdbc90de7691a1b9edb545c17da2d975 and https://gist.github.com/aaronkjones/d996f1a441bc80875fd4929866ca65ad for doing all the hard work!
| #!/bin/bash | |
| # | |
| # A script to update your /etc/hosts file from minikube ingest records | |
| # | |
| # Installation | |
| # ------------ | |
| # curl -L https://gist.github.com/jacobtomlinson/4b835d807ebcea73c6c8f602613803d4/raw/minikube-update-hosts.sh > /usr/local/bin/minikube-update-hosts | |
| # chmod +x /usr/local/bin/minikube-update-hosts | |
| set -e |
| class EventSystem { | |
| constructor() { | |
| this.queue = {}; | |
| } | |
| publish(event, data) { | |
| let queue = this.queue[event]; | |
| if (typeof queue === 'undefined') { | |
| return false; |
Original post : https://unix.stackexchange.com/a/310699
nmcli con add type wifi ifname wlan0 con-name Hostspot autoconnect yes ssid Hostspot
nmcli con modify Hostspot 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
nmcli con modify Hostspot wifi-sec.key-mgmt wpa-psk
nmcli con modify Hostspot wifi-sec.psk "veryveryhardpassword1234"