bashtoni

ROLE_TO_ASSUME="arn:aws:iam::${ACCOUNT_ID}:role/${ROLE_NAME}"
session_token=($(aws sts assume-role --role-arn $ROLE_TO_ASSUME --query 'Credentials.[AccessKeyId,SecretAccessKey,SessionToken]' --role-session-name "$USER-$$" --output text))
export AWS_ACCESS_KEY_ID="${session_token[1]}" AWS_SECRET_ACCESS_KEY="${session_token[2]}" AWS_SESSION_TOKEN="${session_token[3]}"

MarcusFelling

phases:
- phase: CD
  queue: LEP
  steps:
  - task: PowerShell@1
    displayName: ExtConfigs_PreBuild.ps1
    inputs:
            scriptType: filePath
            scriptName: "$(repo.BuildScripts)/ExtConfigs_PreBuild.ps1"
            arguments: ''

maxvt

Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.

This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.

There is a companion feature matrix of various tools. Comments are welcome in the same manner.

danielsdeleo

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant::Config.run do |config|

  config.vm.define 'shortbus' do |c|
    c.vm.box     = "opscode-centos-5.5"
    c.vm.box_url = "http://opscode-vm.s3.amazonaws.com/vagrant/boxes/opscode-centos-5.5.box"
    c.vm.network :hostonly, "192.168.93.93"