install the normal way:
wget https://downloads-packages.s3.amazonaws.com/ubuntu-14.04/gitlab_7.7.2-omnibus.5.4.2.ci-1_amd64.deb & > /dev/null
sudo apt-get update
sudo apt-get upgrade
# Source: https://gist.github.com/820aecf0799d679d9082eef00d07b515 | |
############################################################################# | |
# Bitnami Sealed Secrets # | |
# How To Store Kubernetes Secrets In Git Repositories Without Getting Fired # | |
# https://youtu.be/xd2QoV6GJlc # | |
############################################################################# | |
# Referenced videos: | |
# - What Is GitOps And Why Do We Want It?: https://youtu.be/qwyRJlmG5ew |
install the normal way:
wget https://downloads-packages.s3.amazonaws.com/ubuntu-14.04/gitlab_7.7.2-omnibus.5.4.2.ci-1_amd64.deb & > /dev/null
sudo apt-get update
sudo apt-get upgrade
{ | |
ethereum { | |
smartContractCalls(options: {desc: "block.height", limit: 10}, smartContractMethod: {is: "Contract Creation"}, smartContractType: {is: Token}) { | |
block { | |
height | |
timestamp { | |
time | |
} | |
} | |
smartContract { |
for day of writing, there is a problem with building by dkms this package xtables-addons-common so wehave to install this from source
# Vagrant With Windows, WSL2 and Hyper-V | |
To say getting this configuration working is a pain in the ass is an understatement. However, once it is working correctly you gain access to tools like Ansible and full performance VMs inside Windows. This guide covers the steps I followed to get things working correctly with this configuration. It is possible that something may not work for you however I have been able to reproduce this success on two Windows 11 Pro machines and expect this to work for others. | |
This guide assumes basic knowledge of Windows and Linux systems and how Vagrant operates. Due to the difficulty of setting this up you may need to do some additional troubleshooting | |
## Requirements | |
* Windows Professional - Hyper-V can only be installed on Windows Professional systems or higher | |
* WSL2 - Due to the massive differences between WSL1 and WSL2 this guide will only cover support for WSL2 | |
* CPU Virtualization - While the vast majority of modern CPUs support virtualization you may need to enable it in |
You should have the following completed on your computer before the workshop:
yarn
with brew install yarn
.a4b.amazonaws.com | |
access-analyzer.amazonaws.com | |
account.amazonaws.com | |
acm-pca.amazonaws.com | |
acm.amazonaws.com | |
airflow-env.amazonaws.com | |
airflow.amazonaws.com | |
alexa-appkit.amazon.com | |
alexa-connectedhome.amazon.com | |
amazonmq.amazonaws.com |
#!/bin/bash | |
# Assume the role using locally configured AWS credentials, then pass the assumed role to the container via environment | |
# variables! | |
ASSUMED_ROLE=$(aws sts assume-role \ | |
--role-arn "arn:aws:iam::000000000000:role/our-role-to-assume" \ | |
--role-session-name "session_name" \ | |
--output text) |