aws_assume_role 1.0.4 → 1.0.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 45395edecc7de74806f31e15c043864ba06a56639aed1e5a97e87b3281d5d93a
-  data.tar.gz: 62529589b7c650466430f65af9dea8c46bd73816404017613523be6d84f813d1
+  metadata.gz: 6eeca5db569d6bae9338ddd0b61d633ad984386c1c08d9742fe95ace3b69f819
+  data.tar.gz: d0d5ceed4de70104a8a93174724b27c9de0996f563e7cfd6115bdbd0f3641238
 SHA512:
-  metadata.gz: 9e6b222522697af130f1e791c3118b5b158ceaf4c592a893b640785367a174fb6eac4a4712ebede3796dff293a4404d43bc2fdd6f60fd2ba0490f3bb2656ba74
-  data.tar.gz: 39c9195e410c8b9c37845572b60bce7820859e42a0563bc318c4221f141be39be34886eeaa8bc7b8770893230b1311a4e3776f9ede20a7f8dac440f0dbd4d272
+  metadata.gz: 68f56960cb5620daafd0d7db8b034c92ad0c1934c75ab824601a1a8ae0e82d76f2b3766cf5be23f533599e5586256096f0b1e45ad950ceb544ed09baf9cf90a8
+  data.tar.gz: c3ae138676f4b0e89d49ddba559f1a34e1c45a8b1d49a48ad6ea631bdcb2a6eb6e06a684f3abe2e67bc52b1a93b36e6e961065dce4ebba5dbb9aec21826322bb

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 1.0.5
+* Escape run commands properly (@mrprimate)
+
 ## 1.0.4
 * Ensure ~/.aws exists before saving configuration
 

data/README.md

@@ -9,7 +9,7 @@ aws-assume-role is a utility intended for developer and operator environments
 who need to use 2FA and role assumption to access AWS services.
 
 aws-assume-role can store both AWS access keys and ephemeral session tokens in
-OS credential vaults - Keychain on OSX and Seahorse on Gnome.
+OS credential vaults - Keychain on OSX and Keyring on Gnome.
 
 Why?
 ---
@@ -45,7 +45,7 @@ require introspection bindings as well as Gnone Keyring, by installing one of th
 
 ``` sh
 # Debian/Ubuntu
-apt-get install gnome-keyring libgirepository1.0-dev
+apt-get install gnome-keyring libgirepository1.0-dev libgnome-keyring-common libgnome-keyring-dev
 
 # Fedora
 dnf install gobject-introspection-devel
@@ -65,14 +65,14 @@ aws-assume-role works best if you also store permanent credentials in your keyst
 ``` sh
 > aws-assume-role configure
 Enter the profile name to save into configuration
-company-sso
+company_sso
 Enter the AWS region you would like to default to:
 eu-west-1
 Enter the AWS Access Key ID to use for this profile:
 1234567890010
 Enter the AWS Secret Access Key to use for this profile:
 abcdefghijklmnopqrstuvwzyx1
-Profile `company-sso` saved to '/home/growthsmith/.aws/config'
+Profile `company_sso` saved to '/home/growthsmith/.aws/config'
 ```
 
 ### Configuring roles
@@ -80,7 +80,7 @@ Now that you've set up permanent credentials in your OS credential store, you ca
 set up a role that you will assume in every day use:
 
 ``` sh
-> aws-assume-role configure role -p company-dev --source-profile company-sso  \
+> aws-assume-role configure role -p company-dev --source-profile company_sso  \
 --role-arn=arn:aws:iam::000000000001:role/ViewEC2 --role-session-name=growthsmith \
 --mfa-serial automatic
 ```
@@ -101,9 +101,9 @@ token without prompting for user input. To use this specify
 `--yubikey-oath-name` when calling configure role.
 
 ``` sh
-> aws-assume-role configure role -p company-dev --source-profile company-sso  \
+> aws-assume-role configure role -p company-dev --source-profile company_sso  \
 --role-arn=arn:aws:iam::000000000001:role/ViewEC2 --role-session-name=growthsmith \
---mfa-serial automatic --yubikey-oath-name "Amazon Web Services:myuser@company-sso"
+--mfa-serial automatic --yubikey-oath-name "Amazon Web Services:myuser@company_sso"
 ```
 
 _Yubikey Support_: `aws-assume-role` uses the [smartcard gem](https://rubygems.org/gems/smartcard)
@@ -111,6 +111,17 @@ to connect to the Yubikey, this itself depends upon some C libraries being insta
 [platform specific instructions](https://github.com/costan/smartcard/blob/master/BUILD#L19)
 for installing these libraries PC/SC.
 
+Testing a profile
+-----------------
+You can test a profile using
+```sh
+> aws-assume-role test -p company_sso
+Logged in as:
+    User: 9999999999
+    Account: arn:aws:iam::3333333333:user/username
+    ARN: AIDAIOSWINGTB
+
+```
 
 Running applications
 --------------------
@@ -132,15 +143,24 @@ Please provide an MFA token
 000000
 ```
 
+Listing available profiles
+--------------------------
+Configured profiles can be listed:
+```sh
+> aws-assume-role list
+company_sso
+company2_sso
+company3_sso
+```
 
 Deleting a profile
 ------------------
 If a set of credentials key needs revoking, or the profile isn't relevant anymore:
 ``` sh
-> aws-assume-role delete -p company-sso
-Please type the name of the profile, i.e. company-sso , to continue deletion.
-company-sso
-Profile company-sso deleted
+> aws-assume-role delete -p company_sso
+Please type the name of the profile, i.e. company_sso , to continue deletion.
+company_sso
+Profile company_sso deleted
 ```
 
 Migrating AWS CLI profiles
@@ -149,8 +169,8 @@ It's better to revoke the existing keys and generate new ones. We try to overwri
 file with random data, but this does not take care of ~/.aws/credentials and does not account for SSD wear
 levelling or copy-on-write snapshots.
 ```
-aws-assume-role migrate -p company-sso
-Profile 'company-sso' migrated to keyring.
+aws-assume-role migrate -p company_sso
+Profile 'company_sso' migrated to keyring.
 ```
 
 Exporting environment variables
@@ -184,7 +204,7 @@ Given that `aws-assume-role` has knowledge of your role ARNs via AWS CLI profile
 get to the AWS console for that role/account using
 
 ``` sh
-> aws-assume-role console -p company-sso
+> aws-assume-role console -p company_sso
 ```
 
 `aws-assume-role` will first attempt to log in and get a federated UI link, and

data/lib/aws_assume_role/runner.rb

@@ -14,7 +14,7 @@ class AwsAssumeRole::Runner < Dry::Struct
 
     def initialize(options)
         super(options)
-        command_to_exec = command.join(" ")
+        command_to_exec = command.map(&:shellescape).join(" ")
         process_credentials unless credentials.blank?
         system environment, command_to_exec
         exit_status = $CHILD_STATUS.exitstatus

data/lib/aws_assume_role/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module AwsAssumeRole
-    VERSION = "1.0.4".freeze
+    VERSION = "1.0.5".freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: aws_assume_role
 version: !ruby/object:Gem::Version
-  version: 1.0.4
+  version: 1.0.5
 platform: ruby
 authors:
 - Jon Topper
@@ -14,7 +14,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-11-20 00:00:00.000000000 Z
+date: 2017-12-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -431,7 +431,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.7.2
+rubygems_version: 2.7.3
 signing_key: 
 specification_version: 4
 summary: Manage AWS STS credentials with MFA