git clone https://gist.github.com/dd6f95398c1bdc9f1038.git vault
cd vault
docker-compose up -d
export VAULT_ADDR=http://192.168.99.100:8200
Initializing a vault:
vault init
| #!/bin/bash | |
| AWS_ACCOUNT_ID=012345678901 | |
| # Check if jq is installed | |
| if ! command -v jq &> /dev/null; then | |
| echo "Error: jq is not installed. Please install jq to parse JSON." | |
| exit 1 | |
| fi |
| pip install streamlit | |
| pip install spacy | |
| python -m spacy download en_core_web_sm | |
| python -m spacy download en_core_web_md | |
| python -m spacy download de_core_news_sm |
| pip install streamlit | |
| pip install spacy | |
| python -m spacy download en_core_web_sm | |
| python -m spacy download en_core_web_md | |
| python -m spacy download de_core_news_sm |
| ''' | |
| This is an example of how to send data to Slack webhooks in Python with the | |
| requests module. | |
| Detailed documentation of Slack Incoming Webhooks: | |
| https://api.slack.com/incoming-webhooks | |
| ''' | |
| import json | |
| import requests |
| { | |
| "id": "test", | |
| "modules": { | |
| "cloudtrail": { | |
| "enabled": true, | |
| "event_pattern": { | |
| "source": [ | |
| "aws.ec2" | |
| ] | |
| } |
| --- | |
| # This has been tested with ansible 1.3 with these commands: | |
| # ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts isFirstRun=false" | |
| # ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts isFirstRun=true" | |
| # ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts" | |
| # NB: The type of the variable is crucial! | |
| - name: Ansible Conditionals Examples | |
| hosts: $hosts | |
| vars_files: |
| # Hello, and welcome to makefile basics. | |
| # | |
| # You will learn why `make` is so great, and why, despite its "weird" syntax, | |
| # it is actually a highly expressive, efficient, and powerful way to build | |
| # programs. | |
| # | |
| # Once you're done here, go to | |
| # http://www.gnu.org/software/make/manual/make.html | |
| # to learn SOOOO much more. |
git clone https://gist.github.com/dd6f95398c1bdc9f1038.git vault
cd vault
docker-compose up -d
export VAULT_ADDR=http://192.168.99.100:8200
Initializing a vault:
vault init
| #!groovy | |
| // This is the full syntax for Jenkins Declarative Pipelines as of version 0.8.1. | |
| pipeline { | |
| // Possible agent configurations - you must have one and only one at the top level. | |
| agent any | |
| agent none | |
| agent { | |
| label "whatever" |
| // A Declarative Pipeline is defined within a 'pipeline' block. | |
| pipeline { | |
| // agent defines where the pipeline will run. | |
| agent { | |
| // This also could have been 'agent any' - that has the same meaning. | |
| label "" | |
| // Other possible built-in agent types are 'agent none', for not running the | |
| // top-level on any agent (which results in you needing to specify agents on | |
| // each stage and do explicit checkouts of scm in those stages), 'docker', |