Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a dash of modernity #158

Merged
merged 3 commits into from
Apr 9, 2019
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions .travis.yml
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
language: ruby
sudo: false
rvm:
- 2.0.0-p648
- 2.1.10
- 2.2.6
- 2.3.1
- 2.4.0
- 2.3.8
- 2.4.6
- 2.5.5
- 2.6.1
script: bundle exec rspec
2 changes: 1 addition & 1 deletion opsicle.gemspec
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Gem::Specification.new do |spec|
spec.test_files = Dir['spec/**/*']
spec.require_paths = ["lib"]

spec.add_dependency "aws-sdk", "~> 2"
spec.add_dependency "aws-sdk", ">= 2.0", "< 4.0"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per the AWS upgrade docs, no code changes should be necessary. It'd be great, in a post-v2 world to tweak the dependencies to load just the pieces we need (aws-sdk-s3, aws-sdk-ec2, aws-sdk-opsworks, aws-sdk-iam I think covers it), but I don't think we can do that with v2 still in the mix. As-is, we continue to load the whole universe of AWS SDK code, which leaves us no worse off than with v2 (which was the only option available to us until they broke the pieces apart with v3).

spec.add_dependency "gli", "~> 2.9"
spec.add_dependency "highline", "~> 1.6"
spec.add_dependency "terminal-table", "~> 1.4"
Expand Down