I hereby claim:
- I am robertraybarnes on github.
- I am robertraybarnes (https://keybase.io/robertraybarnes) on keybase.
- I have a public key ASBV_3_9BWRL3j082We3CfqAx9cpuH07mIFOpOUpZCx4rQo
To claim this, I am signing this object:
In order to run this script, you will need to create an EnvironmentDeployment Folder in the root of the C:\ on the target server and place these two files in that folder. This folder contains two files, firstly, a .csv file which contains the user accounts that will be injected into the Active Directory database and the script itself. | |
Let’s get started - The script is a function based script which lets you select which stage of the deployment you would like to undertake. | |
• Open the script called test_environment_deploy.ps1 from the c:\EnvironmentDeploy folder. | |
• Press the run button (This is the play button at the top of the screen) | |
• You will be presented with a pop-up box asking you which action you would like to perform. Select the action you require and click the OK button. | |
• Sit back and let the script do its magic. Repeat these steps for every function you would like to perform |
#!/bin/bash | |
#Jenkins backup script by DevOpsRob | |
#This script requires a git repo called jenkins_backup to be created | |
#You will need to add your ssh public key to the deploy keys of this newly created repo and allow read/write permissions | |
#Clone the repo into /var/lib/ folder | |
#Save this script to the /root/ folder | |
#Setup a crontab to run this script as per your requirement | |
#install git command line tools | |
yum install git -y |
#!/usr/bin/python | |
''' | |
Server Monitoring script to alert in slack by by DevOpsRob | |
Download the slacker python module by running wget https://pypi.python.org/packages/42/f9/3f3bcbe13b8c3aa4a134136cbbaa94beb1c5781f5a33b9317b45c699d453/slacker-0.9.60.tar.gz | |
Untar the file by running tar -xzvf slacker-0.9.60.tar.gz | |
Install the psutil module by yum install python-psutil -y | |
Enter the alert thresholds you would like to set in the variables section | |
For each alert, enter the slack channel name that you would like to notify in place of <slack-channel-name> | |
Install a crontab for this script to run at whatever poll interval you require for your monitoring. e.g. * * * * * /usr/bin/python /root/monitoring/slack_alerting.py | |
This script will also create a log file (/var/log/monitor.log) if it doesn't already exist and write the output of the server checks to it. |
I hereby claim:
To claim this, I am signing this object:
# Local .terraform directories | |
**/.terraform/* | |
# .tfstate files | |
*.tfstate | |
*.tfstate.* | |
# Crash log files | |
crash.log |
What needs to be investigated?
A brief description of what needs to be ascertained / learned through this spike.
Example: Investigate why the provisioning scripts are failing
Scope
Example: options to resolve this issue in all environments
listener "tcp" { | |
address = "0.0.0.0:8200" | |
tls_disable = 1 # TLS will need to be enabled for production | |
tls_min_version = "tls12" | |
} | |
storage "consul" { | |
address = "consul:8500" | |
path = "vault" | |
service = "vault" | |
scheme = "http" |
#!/bin/sh | |
## | |
export AZURE_SUBSCRIPTION_ID= | |
export AZURE_TENANT_ID= | |
export AZURE_CLIENT_ID= | |
export AZURE_CLIENT_SECRET= | |
export ROLE_NAME=spike | |
## | |
vault secrets enable azure |
#!/bin/bash | |
export SUBSCRIPTION_ID= | |
az role definition create --role-definition=<<EOF | |
{ | |
"Name": "vault-admin", | |
"IsCustom": true, | |
"Description": "role for vault to create service principals.", |
--- | |
# simple playbook to demonstrate ansible reading a KV secret from hashicorp vault | |
# the following environment variables need to be set for ansible to authenticate with Vault | |
# | |
# export VAULT_ADDR=http://127.0.0.1:8200 | |
# export VAULT_SKIP_VERIFY=true | |
# export VAULT_AUTHTYPE=token | |
# | |
# A secret will need to be put in the demo/test1 path under the KV secrets engine |