| # temporary hack to address bug with vagrant-vbguest installation | |
| # https://github.com/mitchellh/vagrant/issues/4962 | |
| if awk "BEGIN {exit `vagrant -v` == "1.7.1" ? 0 : 1 }" | |
| then | |
| sudo sed -i .original 's/\*\*opts/opts/g' /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/machine.rb | |
| fi |
All HangOps members are required to comply with the following code of conduct. HangOps admins will enforce this code within HangOps spaces.
Be respectful of other people; respectfully ask people to stop if you are bothered; and if you can’t resolve an issue contact the admins. If you are being a problem, it will be apparent and you may be asked to leave HangOps.
| # Description: | |
| # Incident management | |
| # | |
| # Commands: | |
| # hubot (create|open|start) new incident (on|for|about|of) service-name | |
| moment = require('moment') | |
| # create the incident channel with a custom name + date created | |
| createChannel = (channelName, timestamp, user, robot, msg) -> |
| # set up iam users, groups, roles, policies for cross account sts assume role access | |
| # devs have near full rights to dev account, read access to prod with mfa requirement | |
| # works great with a bit of https://github.com/remind101/assume-role for cli switching | |
| # create a thing in one account vs the other | |
| variable "prod_enable_flag" { | |
| default = { | |
| stage = 0 | |
| prod = 1 |
| { | |
| "AWSEBDockerrunVersion": 2, | |
| "volumes": [ | |
| { | |
| "name": "sock", | |
| "host": { | |
| "sourcePath": "/var/run/docker.sock" | |
| } | |
| }, | |
| { |
| #! /bin/sh | |
| # Userify Shim Installer | |
| # Copyright (c) 2011-2016 Userify Corporation | |
| # How the shim works: | |
| # | |
| # 1. Installer creates /opt/userify/ containing: | |
| # | |
| # a. /opt/userify/creds.py |
| require 'rubygems' | |
| require 'right_aws' | |
| aws_access_key_id = 'your-access-key' | |
| aws_secret_access_key = 'your-secret-key' | |
| target_bucket = 'your-source-bucket' | |
| destination_bucket = 'your-destination-bucket' | |
| s3 = RightAws::S3Interface.new(aws_access_key_id, aws_secret_access_key) |
| ZZZZZZZZ$$$$Z$$$$$$777777III???+++===~~~~~::::::,,,,:,,,,,,,,,:,::::::::::::::::::,,,:,:,::,,,:,:,,,:,,:,:,,,:,,:::,:,:::::~~~~~======++++++?????I?III7II7777777$$$$$$$$$ZZZ$ZZZZZZZ | |
| ZZZZZZZZZ$Z$Z$$$$$$77777IIII???++===~~~~::::~=I7I+I$$$$Z7?,,,,::,::::::::::,:::,,:,,,,,,:,,,,,,,,,,,:,,:,,,,,,,,,,:::,::::~~~~~~===+=++++++???????IIIIIIII77777$$$7$$$$$$$Z$ZZZZZZZZ | |
| ZZZZZZZZZ$$$$$$$$$$$$777IIII???++==~~~~~:~+7$O88888DD8DD88O7+::+::,:::::,,:::::,,,::,,,,,,,,,,,,,,:,,,,,,,,,,,,,,,:::::::::~~~~==?M8N8+++++???????IIIIIII77777777$$$$$$$$$$$$ZZZZZZZ | |
| ZZZZZZ$ZZZZZ$$$$$$$$77777II????++==~~~~~7ZO88DDDDDDNNDDDDDD888OOO7I~::,:,:,::::,,,,,,,,,,,,,,,,,,,,:,,,,,,,,,,,,,,:,:::::~~~~~=7MOZZ==OD++????????IIIIII7I7777777$$$$$$$$$$$$$ZZZZZZ | |
| ZZZZZZZZZZZ$$$$$$$$777777II????++==~~~?Z88DDODDDDDNNNNNNNNDDDDDDD8O$=~:,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,:::::::~~~~INZ$$ZZ+=+=ODI+?????IIIIIIIIIII77777$$$$$$$$$$$$ZZZZZZZ | |
| ZZZZZZZZZZZ$Z$$$$$$$777IIIII???++==~+Z88DDDNO88D88DNNNDNDDNNDNDDD88OO?,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,::: |
| cookbook 'user' |
| [33m[Berkshelf] This version of the Berkshelf plugin has not been fully tested on this version of Vagrant.[0m | |
| [33m[Berkshelf] You should check for a newer version of vagrant-berkshelf.[0m | |
| [33m[Berkshelf] If you encounter any errors with this version, please report them at https://github.com/RiotGames/vagrant-berkshelf/issues[0m | |
| [33m[Berkshelf] You can also join the discussion in #berkshelf on Freenode.[0m | |
| [Berkshelf] Updating Vagrant's berkshelf: '/Users/Adam/.berkshelf/default/vagrant/berkshelf-20130708-21737-op0tog-default' | |
| [Berkshelf] Using apt (1.10.0) | |
| [Berkshelf] Using java (1.9.4) | |
| [Berkshelf] Using tomcat (0.12.0) | |
| [Berkshelf] Using database (1.4.0) | |
| [Berkshelf] Using postgresql (3.0.0) |
