Time-stamp: <2012-03-30 Fri 16:56 README.md>
Author....: 'Mash (Thomas Herbert)
Bacula concurrent jobs multiple storage devices client labeled pools Debian installation and configuration.
Please see http://toshine.org/etc for full article.
| import boto3 | |
| def delete_all_versions(bucket_name): | |
| s3 = boto3.client('s3') | |
| while True: | |
| # List object versions (limited to 1000 per request) | |
| response = s3.list_object_versions(Bucket=bucket_name) | |
| objects_to_delete = [] |
| repos: | |
| ####### | |
| # ALL # | |
| ####### | |
| - repo: git://github.com/pre-commit/pre-commit-hooks | |
| rev: v2.2.3 | |
| hooks: | |
| # Git style | |
| - id: check-added-large-files |
| { | |
| "__inputs": [ | |
| { | |
| "name": "DS_ICINGA2-IDO", | |
| "label": "icinga2-ido", | |
| "description": "", | |
| "type": "datasource", | |
| "pluginId": "mysql", | |
| "pluginName": "MySQL" | |
| } |
| ################################################### | |
| ## | |
| ## Alertmanager YAML configuration for routing. | |
| ## | |
| ## Will route alerts with a code_owner label to the slack-code-owners receiver | |
| ## configured above, but will continue processing them to send to both a | |
| ## central Slack channel (slack-monitoring) and PagerDuty receivers | |
| ## (pd-warning and pd-critical) | |
| ## |
| .......some config..... | |
| alertmanager: | |
| ## Deploy alertmanager | |
| ## | |
| enabled: true | |
| ## Service account for Alertmanager to use. | |
| ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/ | |
| ## |
| 2019/01/10 14:44:07 [DEBUG] plugin: waiting for all plugin processes to complete... | |
| -/+ module.emr.aws_emr_cluster.data_emr_519 (new resource required) | |
| id: "j-1UFF5WCYUON3U" => <computed> (forces new resource) | |
| applications.#: "2" => "2" | |
| applications.1557323817: "Spark" => "Spark" | |
| applications.3006569794: "Hadoop" => "Hadoop" | |
| bootstrap_action.#: "1" => "1" | |
| bootstrap_action.1567847425.args.#: "0" => "0" | |
| bootstrap_action.1567847425.name: "bootstrap" => "bootstrap" | |
| bootstrap_action.1567847425.path: "s3://sf.dev.data.bootstrap.actions/bootstrap.sh" => "s3://sf.dev.data.bootstrap.actions/bootstrap.sh" |
Time-stamp: <2012-03-30 Fri 16:56 README.md>
Author....: 'Mash (Thomas Herbert)
Bacula concurrent jobs multiple storage devices client labeled pools Debian installation and configuration.
Please see http://toshine.org/etc for full article.
I hereby claim:
To claim this, I am signing this object:
| series: | |
| h264: | |
| - 'Downton Abbey': | |
| alternate_name: 'Аббатство Даунтон' | |
| - 'Bones': | |
| alternate_name: 'Кости' | |
| - 'Delirium': | |
| alternate_name: 'Делириум' | |
| - 'Gang Related': | |
| alternate_name: 'Преступные связи' |
The AWS Auto Scaling Goup, configured with a customised Cloud-Init file, sends a notification to an SNS Topic, which in turn passes it onto an SQS queue that the Salt Master is subscribed to. A Reactor watches for the auto scaling events and pre-approves the new minion based on its Auto Scaling group name and instance ID.