aws-cli v.2 comes with a bundled installer and python interpreter:
https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html

For the last couple of weeks, this module has been throwing the following error:

==> default: Error: Could not get latest version: HTTP-Error: 403 Must access using HTTPS instead of HTTP
==> default: Error: /Stage[main]/Awscli/Package[awscli]/ensure: change from 1.10.38 to latest failed: Could not get latest version: HTTP-Error: 403 Must access using HTTPS instead of HTTP

I'm calling it like so:

class { 'awscli':
version => 'latest',
}

And I can't find where to configure this. Any suggestions?

Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, 10 is not a string. It looks to be a Fixnum at /etc/puppetlabs/code/environments/production/modules/concat/manifests/fragment.pp:43:3 at /etc/puppetlabs/code/environments/production/modules/awscli/manifests/profile.pp:101 on node testhost

I'm getting the above error when trying to use create_resources with awscli::profile. Per #40 locking puppetlabs-concat to version '1.2.0' appears to resolve the issue.

I can see that the metadata.json in puppetlabs-concat says it's version 2.2.0, but the forge still lists 1.1.0 as the latest version. And locking the version to 1.2.0 solves the problem.

I'm unfamiliar enough with puppet that I'm hoping someone else can solve that.

The Build is broken, because puppetlabs-concat got a new module dependency with 1.2.1

To fix the build you can

• pin puppetlabs/concat to 1.2.0
• add electrical/file_concat to fixtures

I have both solutions already done, tell me which one you like more:

1: https://github.com/justindowning/puppet-awscli/compare/master...asgoodasnu:fix-dependencies?expand=1

2: https://github.com/justindowning/puppet-awscli/compare/master...asgoodasnu:add-file-concat?expand=1

AWS CLI seems to support other config options next to profiles. For example:

    [preview]
    cloudfront=true

(currently needed for http://docs.aws.amazon.com/cli/latest/reference/cloudfront/index.html)

I am opening this issue to discuss options for implementing this. I currently see two options: either a awscli::preview resource type, or maybe better: a general awscli::configsetting type. The latter might also be used to implement the current awscli::profile.

Any thoughts?

Hi,
I've tried to use this module and it conflicted when tried to install python-* packages with another module(puppet-circus).

'puppet-circus' module assumes that python/pip/virtualenv are already installed and only installs circus related stuff.

Option 1, Specify 'install_python' Boolean parameter to control python installation.
Option 2, Similarly to puppet-circus, remove any python installation related code and inform the user that Python/Pip/other should be available on the host

Thank you,
Yarden

would like to cause awscli::profile to depend on some previous step (creation of user home dir)...
how can I do that?

Because the $title of a resource is used to define a profile name within .aws/credentials, you cannot create the same profile for multiple users; i.e. 'default'. If you attempt to do this, a puppet run will result in duplicate declaration errors.

Resource declarations can be used multiple times in puppet, as opposed to classes (which is one of the main things that differentiate them). This is useful when you want to create multiple files, multiple vhosts, multiple aws creds:

Example:
foo::bar { ‘title’: }
foo::bar { ‘title2’: }
foo::bar { ‘title3’: }

The restriction here is that the resource title must be unique, otherwise you trigger a duplicate declaration error.

Because 'title' is used as a variable within an ERB template for profile creation (i.e., title3 “becomes” the profile name), this approach prohibits you from defining the same profile for different users. As we know, it is very practical to use ‘default’ for different users, as that is what the AWS SDK will use, by default.

The solution is to move the profile name out of the title into a param, and make the corresponding adjustments to variable assignments and .erb template. Thus, you can adhere to the “unique title” requirement of puppet, avoid dup declarations, and still support multiple user accounts using the same profile name, i.e., “default”. Example:

define aws_creds::profile(
$user = 'root',
$aws_profile = 'default',
$aws_access_key_id = undef,
$aws_secret_access_key = undef,
) {
if $aws_access_key_id == undef {
fail ('no aws_access_key_id provided')
}

...
...
concat::fragment{ "${user}${aws_profile}":
target => "${homedir}/.aws/credentials",
content => template('aws_creds/credentials_concat.erb')
}
}

concat.erb:
[<%=@aws_profile%>]
aws_access_key_id=<%=@aws_access_key_id%>
aws_secret_access_key=<%=@aws_secret_access_key%>

Based on http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-multiple-profiles:

The AWS credentials file uses a different naming format than the CLI config file for named profiles. Do not include the 'profile ' prefix when configuring a named profile in the AWS credentials file.

That means, if you have a profile [user2] in ~/.aws/credentials, then the corresponding profile in ~/.aws/config should be [profile user2]. Currently, the generated ~/.aws/config is missing the profile for profile names.

Precondition:

• VM with puppet-server-3.3.1 installed
  • /etc/puppet/manifests/nodes.pp containing an empty node definition for the agent VM
  • /etc/puppet/manifests/site.pp containing a directive to import the nodes file
• VM with Puppet agent installed and provisioned to communicate with the master

Steps to reproduce:

1. On the Puppet master, in the empty node definition, add a block that will invoke awscli::profile with an AWS access key ID, secret access key, and region:

  awscli::profile { 'AWSProfile':
    aws_access_key_id => '[redacted]',
    aws_secret_access_key => '[redacted]',
    aws_region => 'us-east-1',
  }

2. Update (apply) the catalog with the new changes
3. In the Puppet agent VM as a non-root user, apply the update:

sudo puppet agent --test --no-daemonize --server [host name of master VM]

4. In the Puppet agent VM as a non-root user, explore the contents of the newly-created .aws metadata folder in the root user's home:

sudo ls -al /root/.aws

Expected:
The mode of the .aws folder and its contents should, by default, disallow global read access. The official AWS client creates the .aws folder with a mode of 0700 and the files within with a mode of 0600.

Actual:
The mode of the .aws folder and contents are 0755 and 0644 respectively, given the default umask is 0002.

Right now, the module does an 'include epel', but for those who have to set a proxy, they need to be able to pass that param into that module.

What I had to do:

1. deps.pp:

class awscli::deps (
  $proxy = $awscli::params::proxy,
) inherits awscli::params {
  case $::osfamily {
    'Debian': {
      include awscli::deps::debian
    }
    'RedHat': {
      class { 'awscli::deps::redhat':
        proxy => $proxy,
      }
    }
    'Darwin': {
      include awscli::deps::osx
    }
    default:  { fail("The awscli module does not support ${::osfamily}") }
  }
}

1. redhat.pp:

class awscli::deps::redhat (
  $proxy = $awscli::params::proxy,
) inherits awscli::params {
  # Check if we have a proxy to setup with EPEL
  if $proxy != undef {
    class { '::epel':
      epel_proxy => $proxy,
    }
  }
  else {
    include ::epel
  }
  Package { require => Class['epel'] }

  if $awscli::install_pkgdeps {
    if ! defined(Package[ $awscli::pkg_dev ]) {
      package { $awscli::pkg_dev: ensure => installed }
    }
  }
  if $awscli::install_pip {
    if ! defined(Package[ $awscli::pkg_pip ]) {
      package { $awscli::pkg_pip: ensure => installed }
    }
  }
}

1. init.pp:

class awscli (
  $version         = 'present',
  $pkg_dev         = $awscli::params::pkg_dev,
  $pkg_pip         = $awscli::params::pkg_pip,
  $install_pkgdeps = true,
  $install_pip     = true,
  $proxy           = $awscli::params::proxy,
) inherits awscli::params {
  # Handle dependencies
  class { 'awscli::deps':
    proxy => $proxy,
  }

1. params.pp:

class awscli::params {

  $proxy = undef

  case $::osfamily {

In order to use the built-in credentials of an AWS instance, this profile property needs to be supported.

credential_source - The credential provider to use to get credentials for the initial assume-role call. This parameter cannot be provided alongside source_profile. Valid values are:

Environment to pull source credentials from environment variables.
Ec2InstanceMetadata to use the EC2 instance role as source credentials.
EcsContainer to use the ECS container credentials as the source credentials.

I'm trying to test out your module and I can't get it to run. I'm making a simple class and running it inside vagrant (same box as your demo). Puppetfile is attached. Am I missing something?

config.vm.box_url = 'http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210.box'

== Class awsads

class awsads {

notify{ "GOT TO THE CLASS":}

include ::stdlib
include ::awscli

awscli::profile { 'default':
user => 'root',
aws_access_key_id => 'ACCESSKEY',
aws_secret_access_key => 'SECRETKEY',
aws_region => 'us-west-2'
}
}

--------------PUPPETFILE----------

forge "https://forgeapi.puppetlabs.com"

mod 'stahnma/epel', :latest
mod 'puppetlabs/inifile', :latest
mod 'puppetlabs-stdlib'
mod 'jdowning-awscli'
mod 'puppetlabs-concat'

=> default: Error: /Stage[main]/Awsads/Awscli::Profile[default]/Concat[/root/.aws/credentials]/Concat_file[/root/.aws/credentials]: Failed to generate additional resources using 'generate': Invalid parameter show_diff
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/util/errors.rb:60:in fail' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/type.rb:642:in[]='
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/type.rb:2240:in block in set_parameters' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/type.rb:2234:ineach'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/type.rb:2234:in set_parameters' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/type.rb:2196:ininitialize'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/type/file.rb:400:in initialize' ==> default: /tmp/vagrant-puppet/modules-41ee50e0bca8a8f9e6ee7d005b41df51/concat/lib/puppet/type/concat_file.rb:205:innew'
==> default: /tmp/vagrant-puppet/modules-41ee50e0bca8a8f9e6ee7d005b41df51/concat/lib/puppet/type/concat_file.rb:205:in generate' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/transaction.rb:202:ingenerate_additional_resources'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/transaction.rb:222:in block in add_dynamically_generated_resources' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/transaction.rb:222:ineach'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/transaction.rb:222:in add_dynamically_generated_resources' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/transaction.rb:94:inevaluate'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/resource/catalog.rb:144:in apply' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/configurer.rb:122:inblock in apply_catalog'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/util.rb:179:in block in benchmark' ==> default: /opt/ruby/lib/ruby/1.9.1/benchmark.rb:295:inrealtime'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/util.rb:178:in benchmark' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/configurer.rb:121:inapply_catalog'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/configurer.rb:179:in run' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/application/apply.rb:265:inapply_catalog'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/application/apply.rb:213:in main' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/application/apply.rb:146:inrun_command'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/application.rb:364:in block (2 levels) in run' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/application.rb:456:inplugin_hook'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/application.rb:364:in block in run' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/util.rb:504:inexit_on_fail'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/application.rb:364:in run' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/util/command_line.rb:132:inrun'
==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/lib/puppet/util/command_line.rb:86:in execute' ==> default: /opt/ruby/lib/ruby/gems/1.9.1/gems/puppet-3.1.1/bin/puppet:4:in<top (required)>'
==> default: /opt/ruby/bin/puppet:23:in load' ==> default: /opt/ruby/bin/puppet:23:in

I needed to create a symlink for pip-python in /usr/bin in order for the puppet module to install awscli.
For (at least) centOS 7, /usr/bin/pip is the pip binary. I had to add a link in the puppet-awscli module in order to get it to work.

Hi,

Appart from specifying the credentials I want to specify the region name to my ~/.aws/credentials file. Because if you give a role to an ec2 instance and then you install aws-cli with your module just including it by puppet in a node you don't need any credentials, you only need the region to work and I can't find where to specify it.

According to https://forge.puppet.com/stahnma/epel , the current EPEL module should be puppet-epel .

Could you update the dependency when you have a chance? Thank you.

Is this module still maintained and if so, would you support installing the Ubuntu awscli package as a .deb instead of the pip variant?

If you're still maintaining this module, I could try to come up with a PR.

stdlib and concat are already on version > 6. Please update metadata.json

Is puppet 4 support forthcoming?

Running puppet on RHEL 6,

# cat /etc/*release
Red Hat Enterprise Linux Server release 6.8

# puppet --version
3.6.2 (Puppet Enterprise 3.3.1)

Error: Could not set 'present' on ensure: Could not locate the pip command. at 46:/opt/puppet/share/puppet/modules/awscli/manifests/init.pp
Error: Could not set 'present' on ensure: Could not locate the pip command. at 46:/opt/puppet/share/puppet/modules/awscli/manifests/init.pp
Wrapped exception:
Could not locate the pip command.
Error: /Stage[main]/Awscli/Package[awscli]/ensure: change from absent to present failed: Could not set 'present' on ensure: Could not locate the pip command. at 46:/opt/puppet/share/puppet/modules/awscli/manifests/init.pp

I wasn't sure what the "best" fix would be for the module overall, but for this version of Puppet, the workaround I did was this:

In manifests/init.pp:

class awscli (
  $version = 'present',
  $pkg_dev = $awscli::params::pkg_dev,
  $pkg_pip = $awscli::params::pkg_pip
) inherits awscli::params {
  include awscli::deps

  # Workaround for PUP-4997/3829
  file { '/usr/bin/pip-python':
    ensure => 'link',
    target => '/usr/bin/pip',
  }

  package { 'awscli':
    ensure   => $version,
    provider => 'pip',
    require  => [
      Package['python-pip'],
      Class['awscli::deps'],
      File['/usr/bin/pip-python'],
    ],
  }
}

The current version of puppetlabs/stdlib is 8.1.0, and this module blocks upgrades.

The metadata only supports up to puppet 4.x

  "requirements": [
    {
      "name": "puppet",
      "version_requirement": ">= 3.4.3 < 5.0.0"
    }

It would be great if it also supported puppet 5 and 6.

Currently, there is no way to pass a proxy variable to the package command to install awscli via pip.

Something like this:

package { 'awscli':
  ensure   => $version,
  provider => 'pip',
  install_options => '--proxy $proxy'
  require  => [
    Package['python-pip'],  
    Class['awscli::deps'],
  ],
 }

And, should likely make $proxy a class parameter to the init class, and perhaps a default in params.pp. Or, perhaps switch over the presence of a $proxy variable and have two resources for package (one that uses the proxy, one that doesn't).

The dependencies look for python-dev, however on RHEL 6.5 the package is called python-devel as such it fails.

yum search python-dev

...
python-devel.i686 : The libraries and header files needed for Python development
python-devel.x86_64 : The libraries and header files needed for Python development
...

looks like something is wrong here?!

Error: Could not set 'present' on ensure: Could not locate the pip command. at 45:/etc/puppet/modules/awscli/manifests/init.pp Error: Could not set 'present' on ensure: Could not locate the pip command. at 45:/etc/puppet/modules/awscli/manifests/init.pp Wrapped exception: Could not locate the pip command. Error: /Stage[main]/Awscli/Package[awscli]/ensure: change from absent to present failed: Could not set 'present' on ensure: Could not locate the pip command. at 45:/etc/puppet/modules/awscli/manifests/init.pp

Thanks for your help.

Hi there! Could you please release the current version of master to the Puppet forge? There's some goodies (including IAM role support) we're using from a few months back that isn't available in 1.2.0. Thanks!

1.2.0...master

Has anyone tried using this module on Ubuntu 20.04 or newer and/or with Puppet 6 and/or above?

Error: Could not set 'present' on ensure: Could not locate the pip command. at 33:/tmp/modules/awscli/manifests/init.pp
Error: Could not set 'present' on ensure: Could not locate the pip command. at 33:/tmp/modules/awscli/manifests/init.pp

Hey,

Can you please update your module on forge.puppet.com ???

Warning: Module 'puppetlabs-concat' (v2.2.0) fails to meet some dependencies:
  'jdowning-awscli' (v1.3.0) requires 'puppetlabs-concat' (>= 1.0.0 <2.0.0)

1. Here on github in metadata.json you have

{ "name": "puppetlabs/concat", "version_requirement": ">= 1.0.0 <3.0.0" }

2. In module from forge.puppet.com, same version module v1.3.0 has different metadata.json

{"name":"puppetlabs/concat","version_requirement":">= 1.0.0 <2.0.0"}

Also concat is v4.0.0 now so prabably dependecy needs to be updated to <5.0.0

Hi,

I have installed this module into Puppet Enterprise and I am running it against RHEL 6.5.

The puppet logs for the node are constantly showing

notice ensure changed '1.4.1' to '1.4.2' /Stage[main]/Awscli/Package[awscli]/ensure

I am assuming this is pip trying to update awscli from v1.4.1 to v1.4.2?

But it never works and hence tries to apply it every time.

Can we please add support for Amazon Linux. I know it comes pre-installed with AWS Cli. but for version management and etc it might be helpful.

Reproduction steps:

1. /home/david/.gem/ruby/2.3.0/bin/bundle install --path vendor/bundle

2. /home/david/.gem/ruby/2.3.0/bin/bundle exec rake spec :

/home/david/.gem/ruby/2.3.0/bin/bundle exec rake spec 
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/defaults.rb:488: warning: key :queue_type is duplicated and overwritten on line 489
rake aborted!
NameError: uninitialized constant Syck
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor/safe_yaml/lib/safe_yaml/syck_node_monkeypatch.rb:42:in `<top (required)>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor/safe_yaml/lib/safe_yaml.rb:197:in `require'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor/safe_yaml/lib/safe_yaml.rb:197:in `<module:YAML>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor/safe_yaml/lib/safe_yaml.rb:132:in `<top (required)>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor/require_vendored.rb:4:in `require'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor/require_vendored.rb:4:in `<top (required)>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor.rb:40:in `require'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor.rb:40:in `require_libs'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet/vendor.rb:53:in `load_vendored'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet.rb:172:in `<module:Puppet>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppet-3.7.5/lib/puppet.rb:29:in `<top (required)>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/metadata-json-lint-2.1.0/lib/metadata-json-lint/semantic_puppet_loader.rb:21:in `require'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/metadata-json-lint-2.1.0/lib/metadata-json-lint/semantic_puppet_loader.rb:21:in `try_load_puppet'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/metadata-json-lint-2.1.0/lib/metadata-json-lint/semantic_puppet_loader.rb:5:in `try_load'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/metadata-json-lint-2.1.0/lib/metadata_json_lint.rb:6:in `<top (required)>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/metadata-json-lint-2.1.0/lib/metadata-json-lint/rake_task.rb:3:in `require'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/metadata-json-lint-2.1.0/lib/metadata-json-lint/rake_task.rb:3:in `<top (required)>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppetlabs_spec_helper-2.6.2/lib/puppetlabs_spec_helper/rake_tasks.rb:11:in `require'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/puppetlabs_spec_helper-2.6.2/lib/puppetlabs_spec_helper/rake_tasks.rb:11:in `<top (required)>'
/home/david/code/puppet-r10k/modules/puppet-awscli/Rakefile:2:in `require'
/home/david/code/puppet-r10k/modules/puppet-awscli/Rakefile:2:in `<top (required)>'
/home/david/code/puppet-r10k/modules/puppet-awscli/vendor/bundle/ruby/2.3.0/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)

Happens with both master and tag 2.0.0.

Thanks!