ey-core 3.4.4 → 3.6.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 60c37b8856b7cd6b06d2996a64d376bbb170f75f
-  data.tar.gz: 17060911ccff177a709c111a1916fc8d42b3dadb
+SHA256:
+  metadata.gz: cbeda06f2f514d3034e222ec30017cc9f0a7c6a1c563c28c2ae55b221020a51e
+  data.tar.gz: 79abeedf991f07a13d70f25bf452598b3b5b0e44b31f1647c5b9c1238c8184d2
 SHA512:
-  metadata.gz: 3911ac7f2dab3d27fa225e563e9abb46f6ab2b4a95ee82153a70668480f56a751a2623c731a24cfbc17efc0615c6f7d56e210af24b01ceeb458833aee45a8ba3
-  data.tar.gz: fb4d4e6c23f50159d54c784e07fd62c63998b33d9930a67c57e1e364fc7a0fd917f9e4d11c58b31a3ae0108278dfe09504162f35b17ad8a6d47e17209f07138d
+  metadata.gz: de038dc51dff193d6fc14fce50bd6e1541b6eb56dfae42233e7cacef1eacab75c09b5cafeba68f1169d5951d45a05b0a005a8582d6512e279d569b3974b3bd3d
+  data.tar.gz: 7de16ef2c589096b9b2c6bf487ceb333079117999e9ae3f1b2c496b9e9a1f45948d8b5370f8ca1e560a4621b36d36bc9493de24b378c30dda4c25aac9e5e8b14

data/.ruby-version

@@ -1 +1 @@
-2.2.2
+2.5.8

data/CHANGELOG.md

@@ -1,13 +1,35 @@
 # Change Log
 
-## [Unreleased](https://github.com/engineyard/core-client-rb/tree/HEAD)
+## [Unreleased](https://github.com/engineyard/core-client-rb/tree/develop)
 
-[Full Changelog](https://github.com/engineyard/core-client-rb/compare/v2.8.4...HEAD)
+[Full Changelog](https://github.com/engineyard/core-client-rb/compare/v3.6.1...develop)
 
 **Merged pull requests:**
 
-- \[ENG-193\] Create untracked addresses via smithy [\#34](https://github.com/engineyard/core-client-rb/pull/34) ([omgitsads](https://github.com/omgitsads))
-- remove usage of hmac client in specs [\#33](https://github.com/engineyard/core-client-rb/pull/33) ([lanej](https://github.com/lanej))
+## [v3.6.1](https://github.com/engineyard/core-client-rb/tree/v3.6.1) (2020-06-11)
+
+[Full Changelog](https://github.com/engineyard/core-client-rb/compare/v3.5.0...v3.6.1)
+
+**Merged pull requests:**
+
+- Adds support for Docker credentials [\#106](https://github.com/engineyard/core-client-rb/pull/106) ([nodecarter](https://github.com/nodecarter))
+- Adds support for container discovery [\#107](https://github.com/engineyard/core-client-rb/pull/107) ([thorn](https://github.com/thorn))
+- Fixes `get_deployment` request parameters [\#108](https://github.com/engineyard/core-client-rb/pull/108) ([lucis-fluxum](https://github.com/lucis-fluxum))
+- Adds server names to server list output [\#112](https://github.com/engineyard/core-client-rb/pull/112) ([glennr](https://github.com/glennr))
+- Fixes the `--no-migrate` flag for `ey-core deploy` [\#114](https://github.com/engineyard/core-client-rb/pull/114) ([mushyy](https://github.com/mushyy))
+- Upgrades dependencies and adds ruby-2.7 support for the gem [\#120](https://github.com/engineyard/core-client-rb/pull/120) ([ssuttner](https://github.com/ssuttner))
+- Adds a bit of CLI documentation [\#121](https://github.com/engineyard/core-client-rb/pull/121) ([ess](https://github.com/ess))
+
+## [v3.5.0](https://github.com/engineyard/core-client-rb/tree/v3.5.0) (2018-04-04)
+[Full Changelog](https://github.com/engineyard/core-client-rb/compare/v3.4.4...v3.5.0)
+
+**Merged pull requests:**
+
+- Add support for autoscaling policies [\#110](https://github.com/engineyard/core-client-rb/pull/101) ([thorn](https://github.com/thorn))
+- Add support for environment variables [\#90](https://github.com/engineyard/core-client-rb/pull/90) ([rzaharenkov](https://github.com/rzaharenkov))
+- Add ability to send configuration options together with blueprint [\#104](https://github.com/engineyard/core-client-rb/pull/104) ([ramonpm](https://github.com/ramonpm))
+- Add support for address.scope parameter for EIP [\#102](https://github.com/engineyard/core-client-rb/pull/102) ([thorn](https://github.com/thorn))
+- Various fixes for `servers` command [\#103](https://github.com/engineyard/core-client-rb/pull/103) ([binarypaladin](https://github.com/binarypaladin))
 
 ## [v2.8.4](https://github.com/engineyard/core-client-rb/tree/v2.8.4) (2015-08-12)
 [Full Changelog](https://github.com/engineyard/core-client-rb/compare/v2.8.3...v2.8.4)
@@ -164,4 +186,4 @@
 
 
 
-\* *This Change Log was automatically generated by [github_changelog_generator](https://github.com/skywinder/Github-Changelog-Generator)*
+\* *This Change Log was automatically generated by [github_changelog_generator](https://github.com/skywinder/Github-Changelog-Generator)*

data/Gemfile

@@ -3,7 +3,7 @@ source 'https://rubygems.org'
 # Specify your gem's dependencies in ey-core.gemspec
 gemspec
 
-gem "rack", "<= 2.0"
+gem "rack", "<= 2.1.4"
 
 group :doc do
   gem 'yard'
@@ -13,7 +13,6 @@ end
 group :test do
   gem 'codeclimate-test-reporter', '~> 0.3'
   gem 'faker'
-  gem 'hashie'
   gem 'rack-test'
   gem 'rspec', '~> 3.1'
   gem 'simplecov'

data/README.md

@@ -1,8 +1,8 @@
-# Ey::Core
+# Ey::Core #
 
-Official Ruby Engine Yard Core API Client.
+Official Engine Yard Core API Ruby client and CLI utility.
 
-## Installation
+## Installation ##
 
 Add this line to your application's Gemfile:
 
@@ -12,11 +12,68 @@ And then execute:
 
     $ bundle
 
-Or install it yourself as:
+Or install it yourself for ad-hoc or CLI usage:
 
     $ gem install ey-core
 
-## Usage
+## Usage ##
+
+There are two ways to use this gem: you can install it to use as a client library for writing your own Engine Yard Cloud integrations, or you can use the `ey-core` CLi app to use our curated integrations.
+
+### CLI Usage ###
+
+The CLI app, `ey-core`, is the replacement for the `ey` command that was provided by the now mostly deprecated`engineyard` gem. The old gem is still updated as need be, but is effectively just a slightly different UI for the `ey-core` command.
+Like the `git` command, `ey-core` is like a gateway to other commands.
+
+Rather than attempting to provide an exhaustive writeup of all of the commands provided by `ey-core`, this document will instead describe what are likely the most common use cases and leave you to read up on the remainder via the `help` command.
+
+#### Use Case: Getting Help ####
+
+Arguably the most important command in the app is `ey-core help`. Given no arguments, it provides the list of second-level commands avaiable for use. From that point, each argument is expected to be a command from the next level of the hierarchy.
+
+For example, if one wishes to learn about the `servers` second-level command, they would do `ey-core help servers`.
+
+For commands in even deeper levels, one just adds each level of chain after the `help` command. Try this in your terminal: `ey-core help recipes apply`
+
+#### Use Case: Deploying An App ####
+
+The `ey-core deploy` command allows one to deploy a new revision of an existing application in an existing environment. The command itself has several options, some of which may or may not be required depending on several factors. To guarantee the best result and remove a good deal of uncertainty in the process, we've opted to describe a somewhat verbose invocation of the command in this document.
+
+Let's start with some assumptions:
+
+* The name of our Engine Yard account is `MyAwesomeCompany` (you can get a real account name with `ey-core accounts`)
+* That account has an environment named `awesome_production` (you can get a real environment name with `ey-core environments`)
+* That account has an application named `awesome_app` (you can get a real application name with `ey-core applications`)
+* The aforementioned application is already associated with the environment
+
+As mentioned, some of the options for the `deploy` command are optional, and all of the topics discussed in our assumptions are effectively optional. That said, we suggest specifying *all* of these options to ensure absolutely that the proper application is deployed to the proper environment in the proper account.
+
+All that said, to deploy the application to its latest git ref and the same migration command as the last deployment, you would issue the following command:
+
+`$ ey-core deploy --account MyAwesomeCompany --environment awesome_production --app awesome_app`
+
+You can also specify a git ref to use if you'd like to deploy a specific version or branch of the app:
+
+`$ ey-core deploy --account MyAwesomeCompany --environment awesome_production --app awesome_app --ref feature/new-ui`
+
+Say that you want to change the way your migrations are run during the deploy. You can specify the migration command:
+
+`$ ey-core deploy --account MyAwesomeCompany --environment awesome_production --app awesome_app --migrate 'bundle exec rake db:migrate:new_hotness'`
+
+Additionally, if you wish to skip migrations for the deployment, you can do that, too:
+
+`$ ey-core deploy --account MyAwesomeCompany --environment awesome_production --app awesome_app --no-migrate`
+
+Any of the invocations that we've talked about so far will stream the deployment log as it runs. If you'd rather do a fire-and-forget style deployment and check in on it later, you can add the `--no-wait` flag. If, however, you'd like to see even more information spit out during the deploy, you can add the `--verbose` flag.
+
+That's about all there is to deployment so long as you consider the application, environment, and account to be required options. You can read more about any of the commands that we've mentioned in this use case by running the following in your terminal:
+
+* `ey-core help accounts`
+* `ey-core help applications`
+* `ey-core help deploy`
+* `ey-core help environments`
+
+### Client Library Usage ###
 
 Uses [cistern](https://github.com/lanej/cistern) to wrap RESTful resources nicely.
 
@@ -30,7 +87,7 @@ client.users.current  # =>
 >
 ```
 
-### Authentication
+#### Authentication ####
 
 * Via Token
 
@@ -48,7 +105,7 @@ Ey::Core::Client.new(
 )
 ```
 
-### Mock
+#### Mock ####
 
 Mock is disabled by default.
 
@@ -64,7 +121,7 @@ Reset the mock
 Ey::Core::Client.reset!
 ```
 
-### Testing
+#### Testing ####
 
 By default, specs are run against the core mock. In order to run them against awsm mocked mode instead, run `MOCK_CORE=false bundle exec rspec`
 

data/ey-core.gemspec

@@ -18,22 +18,23 @@ Gem::Specification.new do |gem|
   gem.require_paths = ["lib"]
   gem.licenses      = ["MIT"]
 
-  gem.required_ruby_version = ">= 2.2.2"
+  gem.required_ruby_version = ">= 2.5"
 
   gem.add_dependency "addressable"
 
-  gem.add_dependency "awesome_print"
+  gem.add_dependency "amazing_print", "~> 1.1.0"
   gem.add_dependency "belafonte"
   gem.add_dependency "cistern", "~> 0.12.3"
   gem.add_dependency "colorize"
   gem.add_dependency "ey-hmac", "~> 2.0"
   gem.add_dependency "escape"
-  gem.add_dependency "faraday", "~> 0.9"
-  gem.add_dependency "faraday_middleware", "~> 0.9"
+  gem.add_dependency "hashie", "~> 4.1.0"
+  gem.add_dependency "faraday", "~> 1.0"
+  gem.add_dependency "faraday_middleware", "~> 1.0"
   gem.add_dependency "rack"
   gem.add_dependency "faye"
   gem.add_dependency "highline"
-  gem.add_dependency "json", "< 2.0"
+  gem.add_dependency "json", "~> 2.3.0"
   gem.add_dependency "mime-types"
   gem.add_dependency "oj"
   gem.add_dependency "oj_mimic_json"

data/features/docker_registry_credentials.feature

@@ -0,0 +1,21 @@
+Feature: Docker Registry Credentials
+  In order to authorize the Docker Engine with the AWS ECR registry
+  As a User
+  I want to be able to retrieve the Docker authorization credentials
+
+  Background:
+    Given I'm an Engine Yard user
+    And ey-core is configured with my cloud token
+    And I have the following accounts:
+      | Account Name  |
+      | one           |
+      | two           |
+
+  Scenario Outline: Retrieving Docker authorization credentials
+    When I run `ey-core get-docker-registry-login <Account Flag> one <Location Flag> us-east-1`
+    Then I see the docker login command
+
+    Examples:
+      | Account Flag  | Location Flag |
+      | -c            | -l            |
+      | --account     | --location    |

data/features/environment_variables.feature

@@ -0,0 +1,54 @@
+Feature: Environment Variables
+  In order to know current values of environment variables assigned to my Engine Yard environments
+  As a User
+  I want to be able to list the environment variables for environments which I'm associated
+
+  Background:
+    Given I'm an Engine Yard user
+    And ey-core is configured with my cloud token
+    And I have the following accounts:
+      | Account Name  |
+      | one           |
+      | two           |
+      | three         |
+    And I have the following applications:
+      | Account Name  | Application Name |
+      | one           | blog_app         |
+      | two           | todo_app         |
+    And I have the following environments:
+      | Application Name  | Environment Name  |
+      | blog_app          | staging           |
+      | blog_app          | production        |
+      | todo_app          | staging           |
+    And I have the following environment variables:
+      | Name          | Value               | Application Name  | Environment Name  | Sensitive |
+      | SECRET_BASE   | abc=                | blog_app          | staging           | false     |
+      | DB_PASSWORD   | 123qweasd!!         | blog_app          | staging           | true      |
+      | SECRET_BASE   | qwe=                | blog_app          | production        | false     |
+      | DB_PASSWORD   | 987qweasd!!         | blog_app          | production        | true      |
+      | DB_PASSWORD   | my_secure_password  | todo_app          | staging           | true      |
+
+  Scenario: Listing all of my environment variables
+    When I run `ey-core environment_variables`
+    Then I see the name and value for all of my environments as well as name of associated environment and application
+
+  Scenario Outline: Listing environment variables for a specific environment
+    When I run `ey-core environment_variables <Environment Flag> staging`
+    Then I see the environment variables associated with `staging` environment
+    But I do not see environment variables associated with any other environments different from `staging`
+
+    Examples:
+      | Environment Flag  |
+      | -e                |
+      | --environment     |
+
+  Scenario Outline: Listing environment variables for a specific application
+    When I run `ey-core environment_variables <Application Flag> blog_app`
+    Then I see the environment variables associated with `blog_app` application
+    But I do not see environment variables associated with any other applications different from `blog_app`
+
+    Examples:
+      | Application Flag  |
+      | -a                |
+      | --application     |
+

data/features/step_definitions/accounts_steps.rb

@@ -15,6 +15,20 @@ Given %(I'm associated with several accounts) do
   memorize_fact(:accounts, [account1, account2])
 end
 
+Given %r(^I have the following accounts:$) do |account_names|
+  account_names.hashes.each do |account_hash|
+    known_accounts.push(
+      create_account(
+        client: client,
+        owner: current_user,
+        account: {
+          name: account_hash['Account Name']
+        }
+      )
+    )
+  end
+end
+
 Then %(I see the name and ID of each of my accounts) do
   recall_fact(:accounts).each do |account|
     expect(output_text).to include(account.id)

data/features/step_definitions/applications_steps.rb

@@ -1,17 +1,3 @@
-Given %r(^I have the following accounts:$) do |account_names|
-  account_names.hashes.each do |account_hash|
-    known_accounts.push(
-      create_account(
-        client: client,
-        owner: current_user,
-        account: {
-          name: account_hash['Account Name']
-        }
-      )
-    )
-  end
-end
-
 Given %(each of my accounts has several applications) do
   known_accounts.each do |account|
     known_apps.push(
@@ -24,6 +10,13 @@ Given %(each of my accounts has several applications) do
   end
 end
 
+Given(/^I have the following applications:$/) do |applications|
+  applications.hashes.each do |application_hash|
+    account = known_accounts.find { |acc| acc.name == application_hash['Account Name'] }
+    known_apps.push(create_application(account: account, name: application_hash['Application Name']))
+  end
+end
+
 Then %(I see the name and ID for all of my applications) do
   known_apps.each do |app|
     expect(output_text).to match(/#{Regexp.escape(app.id.to_s)}\s+\|\s+#{Regexp.escape(app.name)}/)

data/features/step_definitions/docker_registry_credentials_steps.rb

@@ -0,0 +1,3 @@
+Then %(I see the docker login command) do
+  expect(output_text).to match("docker login -u foo -p bar https://012345678901.dkr.ecr.us-east-1.amazonaws.com")
+end

data/features/step_definitions/environment_variables_steps.rb

@@ -0,0 +1,51 @@
+Given(/^I have the following environment variables:$/) do |variables|
+  variables.hashes.each do |variable_hash|
+    application = known_apps.find { |app| app.name == variable_hash['Application Name'] }
+    environment = known_environments.find { |env| env.name == variable_hash['Environment Name'] }
+    known_environment_variables.push(
+      create_environment_variable(
+        application: application,
+        environment: environment,
+        environment_variable: {
+          name: variable_hash['Name'],
+          value: variable_hash['Value'],
+          sensitive: variable_hash['Sensitive']
+        }
+      )
+    )
+  end
+end
+
+Then(/^I see the name and value for all of my environments as well as name of associated environment and application$/) do
+  known_environment_variables.each do |environment_variable|
+    expect(output_text).to match(match_environment_variable_regexp(environment_variable))
+  end
+end
+
+Then(/^I see the environment variables associated with `(\w+)` environment$/) do |environment_name|
+  known_environment_variables.each do |environment_variable|
+    next unless environment_variable.environment_name == environment_name
+    expect(output_text).to match(match_environment_variable_regexp(environment_variable))
+  end
+end
+
+Then(/^I do not see environment variables associated with any other environments different from `(\w+)`$/) do |environment_name|
+  known_environment_variables.each do |environment_variable|
+    next if environment_variable.environment_name == environment_name
+    expect(output_text).not_to match(match_environment_variable_regexp(environment_variable))
+  end
+end
+
+Then(/^I see the environment variables associated with `(\w+)` application$/) do |application_name|
+  known_environment_variables.each do |environment_variable|
+    next unless environment_variable.application_name == application_name
+    expect(output_text).to match(match_environment_variable_regexp(environment_variable))
+  end
+end
+
+Then(/^I do not see environment variables associated with any other applications different from `(\w+)`$/) do |application_name|
+  known_environment_variables.each do |environment_variable|
+    next if environment_variable.application_name == application_name
+    expect(output_text).not_to match(match_environment_variable_regexp(environment_variable))
+  end
+end

data/features/step_definitions/environments_steps.rb

@@ -14,6 +14,21 @@ Given %(each of my applications has an environment) do
   end
 end
 
+Given(/^I have the following environments:$/) do |environments|
+  environments.hashes.each do |environment_hash|
+    application = known_apps.find { |app| app.name == environment_hash['Application Name'] }
+    known_environments.push(
+      create_environment(
+        account: application.account,
+        application: application,
+        environment: {
+          name: environment_hash['Environment Name']
+        }
+      )
+    )
+  end
+end
+
 Then %(I see the name and ID for all of my environments) do
   known_environments.each do |environment|
     expect(output_text).to match(/#{Regexp.escape(environment.id.to_s)}\s+\|\s+#{Regexp.escape(environment.name)}/)

data/features/support/environment_variable_helpers.rb

@@ -0,0 +1,20 @@
+module EnvironmentVariableHelpers
+  ENVIRONMENT_VARIABLE_DISPLAY_FIELDS = %i[id name value environment_name application_name]
+
+  def known_environment_variables
+    begin
+      recall_fact(:environment_variables)
+    rescue
+      memorize_fact(:environment_variables, [])
+    end
+  end
+
+  def match_environment_variable_regexp(environment_variable)
+    regexp_parts = ENVIRONMENT_VARIABLE_DISPLAY_FIELDS.map do |field|
+      Regexp.escape(environment_variable.send(field).to_s)
+    end
+    Regexp.new(regexp_parts.join("(\s+)\\|(\s+)"))
+  end
+end
+
+World(EnvironmentVariableHelpers)

data/features/support/mock_api.rb

@@ -1,7 +1,6 @@
 require 'cucumber/rspec/doubles'
 
 # Set up the mocks. Ookla would approve.
-Cistern.formatter = Cistern::Formatter::AwesomePrint
 Ey::Core::Client.mock!
 Ey::Core::Client::Mock.timeout = 0.1
 Ey::Core::Client::Mock.poll_interval = 0

data/features/support/resource_helpers.rb

@@ -127,6 +127,18 @@ module ResourceHelpers
     environment
   end
 
+  def create_environment_variable(options={})
+    application = options[:application] || create_application
+    environment = options[:environment] || create_environment
+
+    environment_variable = options[:environment_variable] || {}
+    environment_variable.merge!(application_id: application.id, environment: environment.id)
+    environment_variable[:name] ||= SecureRandom.hex(8)
+    environment_variable[:value] ||= SecureRandom.hex(32)
+
+    client.environment_variables.create!(environment_variable)
+  end
+
   def create_provider_location(client, attributes={})
     attributes = Cistern::Hash.stringify_keys(attributes)
 

data/lib/ey-core/cli/deploy.rb

@@ -32,6 +32,11 @@ module Ey
           long: "migrate",
           description: "The migration command to run.  This option has a 50 character limit.",
           argument: "migrate"
+        option :serverside_version,
+          short: "S",
+          long: "serverside_version",
+          description: "Override the default version of engineyard-serverside. The version must match a released version. Use with care.",
+          argument: "serverside_version"
 
         option :app,
           short: "a",
@@ -43,11 +48,6 @@ module Ey
           long: "no-wait",
           description: "Don't wait for deploy to finish, exit after deploy is started"
 
-        switch :verbose,
-          short: "v",
-          long: "verbose",
-          description: "Deploy with verbose output"
-
         switch :verbose,
           short: "v",
           long: "verbose",
@@ -63,7 +63,7 @@ module Ey
             abort <<-EOF
 Found account #{operator.name} but requested account #{option(:account)}.
 Use the ID of the account instead of the name.
-This can be retrieved by running "ey accounts".
+This can be retrieved by running "ey-core accounts".
 EOF
             .red unless operator.name == option(:account) || operator.id == option(:account)
           end
@@ -78,8 +78,11 @@ EOF
 
           app = core_application_for(environment, self.options)
 
-          deploy_options = {verbose: options[:verbose], cli_args: ARGV}
+          deploy_options = {verbose: switch_active?(:verbose), cli_args: ARGV}
           latest_deploy = nil
+	  if options[:serverside_version]
+            deploy_options.merge!(serverside_version: option(:serverside_version))
+          end
           if options[:ref]
             deploy_options.merge!(ref: option(:ref))
           else
@@ -93,12 +96,12 @@ EOF
           end
           if (option(:migrate) || switch_active?(:no_migrate))
             deploy_options.merge!(migrate_command: option(:migrate)) if option(:migrate)
-            deploy_options.merge!(migrate_command: '') if switch_active?(:no_migrate)
+            deploy_options.merge!(migrate_command: nil) if switch_active?(:no_migrate)
           else
             puts "missing migrate option (--migrate or --no-migrate), checking latest deploy...".yellow
             latest_deploy ||= environment.latest_deploy(app)
             if latest_deploy
-              deploy_options.merge!(migrate_command: (latest_deploy.migrate && latest_deploy.migrate_command) || '')
+              deploy_options.merge!(migrate_command: (latest_deploy.migrate && latest_deploy.migrate_command) || nil)
             else
               raise "either --migrate or --no-migrate needs to be specified"
             end

data/lib/ey-core/cli/docker_registry_login.rb

@@ -0,0 +1,29 @@
+require 'ey-core/cli/subcommand'
+
+module Ey
+  module Core
+    module Cli
+      class DockerRegistryLogin < Subcommand
+        title "get-docker-registry-login"
+        summary "Prints the docker login command to authorize the Docker Engine with the AWS ECR registry"
+
+        option :account,
+               short:       'c',
+               long:        'account',
+               description: 'Name or ID of the account that the environment resides in.',
+               argument:    'Account name or id'
+
+        option :location,
+               short:       'l',
+               long:        'location',
+               description: 'ECR availability regions',
+               argument:    'Location name'
+
+        def handle
+          credentials = core_account.retrieve_docker_registry_credentials(option(:location))
+          stdout.puts "docker login -u #{credentials.username} -p #{credentials.password} #{credentials.registry_endpoint}"
+        end
+      end
+    end
+  end
+end

data/lib/ey-core/cli/environment_variables.rb

@@ -0,0 +1,71 @@
+require 'ey-core/cli/subcommand'
+require 'ey-core/cli/helpers/stream_printer'
+
+module Ey
+  module Core
+    module Cli
+      class EnvironmentVariables < Subcommand
+        MASK = '****'.freeze
+        SYMBOLS_TO_DISPLAY = 4
+        MAX_LENGTH_TO_DISPLAY = 30
+
+        include Ey::Core::Cli::Helpers::StreamPrinter
+
+        title "environment_variables"
+        summary "Retrieve a list of Engine Yard environment variables for environments that you have access to."
+
+        option :environment,
+          short: 'e',
+          long: 'environment',
+          description: 'Filter by environmeent name or id',
+          argument: 'Environment'
+
+        option :application,
+          short: 'a',
+          long: 'application',
+          description: 'Filter by application name or id',
+          argument: 'Application'
+
+        switch :display_sensitive,
+          short: 's',
+          long: 'display_sensitive',
+          description: 'Determines whether values of sensitive variables should be printed',
+          argument: 'Display Sensitive'
+
+        def handle
+          environment_variables = if option(:application)
+                                    core_applications(option(:application)).flat_map(&:environment_variables)
+                                  elsif option(:environment)
+                                    core_environments(option(:environment)).flat_map(&:environment_variables)
+                                  else
+                                    core_environment_variables
+                                  end
+
+          stream_print("ID" => 10, "Name" => 30, "Value" => 50, "Environment" => 30, "Application" => 30) do |printer|
+            environment_variables.each_entry do |ev|
+              printer.print(ev.id, ev.name, print_variable_value(ev), ev.environment_name, ev.application_name)
+            end
+          end
+        end
+
+        private
+
+        def print_variable_value(environment_variable)
+          if environment_variable.sensitive && !switch_active?(:display_sensitive)
+            hide_sensitive_data(environment_variable.value)
+          else
+            environment_variable.value
+          end
+        end
+
+        def hide_sensitive_data(value)
+          if value.length > SYMBOLS_TO_DISPLAY
+            MASK + value[-SYMBOLS_TO_DISPLAY, SYMBOLS_TO_DISPLAY]
+          else
+            MASK
+          end
+        end
+      end
+    end
+  end
+end

data/lib/ey-core/cli/helpers/chef.rb

@@ -28,7 +28,7 @@ module Ey
               puts "#{type.capitalize} chef run failed".red
               ap request
               if server = environment.servers.first
-                puts "For logs try `ey logs --server #{server.provisioned_id}` --environment #{environment.name}"
+                puts "For logs try `ey-core logs --server #{server.provisioned_id}` --environment #{environment.name}"
               end
             end
           end