Heroku gem is being sunset
Closed this issue · 18 comments
http://blog.heroku.com/archives/2012/10/15/upgrading-to-the-heroku-toolbelt/
Looks like updates to the Heroku gem are going to stop in December. Does heroku_san even need the heroku gem dependency anymore now that heroku-api exists?
I believe that everything heroku_san does can be done with heroku-api, it's just work that must be completed.
Not too much left to do, either.
Sent from my iPhone ~ 808.722.6142
On Oct 15, 2012, at 3:37 PM, Ryan Ahearn notifications@github.com wrote:
I believe that everything heroku_san does can be done with heroku-api, it's just work that must be completed.
—
Reply to this email directly or view it on GitHub.
Anyone is taking care of it? The Network graph is not working for me so I can't really see if someone took a shot at it. Is there more to do than just remove the dependency?
There are some actions that need to be redone to use the API. It's not
hard, but it's not trivial, eithet
On Tuesday, October 23, 2012, Pierre Olivier Martel wrote:
Anyone is taking care of it? The Network graph is not working for me so I
can't really see if someone took a shot at it. Is there more to do than
just remove the dependency?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/108#issuecomment-9707122.
Can you elaborate on what needs to be done, and whether anyone is taking care of it? I'd be happy to contribute, but don't want to step on toes / run in circles.
I started on it last week. Mostly it is about dropping the dependency and running through the failing tests. My current block is that rvm changed and it is breaking Aruba, so cucumber -p remote tests are failing.
Best advice is to make a branch, get things green and make a pull request.
Ken
Sent from my iPhone ~ 808.722.6142
On Oct 29, 2012, at 9:04 AM, Alex Heaton notifications@github.com wrote:
Can you elaborate on what needs to be done, and whether anyone is taking care of it? I'd be happy to contribute, but don't want to step on toes / run in circles.
—
Reply to this email directly or view it on GitHub.
Hi Ken :D (MIlyoni devs here). We are also having issues as of today (11-6-2012) with some of the commands used by the heroku san gem. I'm sure other people are also experiencing these issues now too.
Almost done. My changes aren't compatible with Ruby 1.8.7: https://travis-ci.org/fastestforward/heroku_san/jobs/3120179
Hm, so are there certain tasks that can't be done using only heroku-api?
No, not exactly. There's a lot of infrastructure around running a job and tail'ing the output. It's easier -- much easier -- to let the toolbelt handle it just like the old gem did. heroku_san is not a replacement for the heroku CLI tool, just a helper for some common Rails (et al) tasks.
Hi,
heroku_san stopped working without heroku gem.
Toolbelt is installed and I'm using Ruby 1.9.3-p194/Rails 3.2.9.
Can you please help??
git update-ref -d refs/heroku_san/deploy
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/bundler-1.2.0/lib/bundler/rubygems_integration.rb:147:in block in replace_gem': heroku is not part of the bundle. Add it to Gemfile. (Gem::LoadError) from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/heroku:18:in
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval' from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/bundler-1.2.0/lib/bundler/rubygems_integration.rb:147:in
block in replace_gem': heroku is not part of the bundle. Add it to Gemfile. (Gem::LoadError) from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/heroku:18:in
'from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval' from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
'rake aborted!
Command failed with status (1): [heroku run rake db:migrate --app admin-staging-fresca]
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/stage.rb:148:in
sh_heroku' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/stage.rb:51:in
run'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/deploy/rails.rb:9:in
deploy' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/stage.rb:66:in
deploy'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/tasks.rb:209:in
block (3 levels) in <top (required)>' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/project.rb:66:in
block in each_app'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/project.rb:65:in
each' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/project.rb:65:in
each_app'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/tasks.rb:321:in
each_heroku_app' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/tasks.rb:208:in
block (2 levels) in <top (required)>'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
'Tasks: TOP => deploy => heroku:deploy
(See full trace by running task with --trace)
Are you using heroku_san v4.0.x? It has support for the tool belt.
Ken
On Fri, Nov 23, 2012 at 3:12 AM, Dano Lee notifications@github.com wrote:
Hi,
heroku_san stopped working without heroku gem.
Toolbelt is installed and I'm using Ruby 1.9.3-p194/Rails 3.2.9.Can you please help??
git update-ref -d refs/heroku_san/deploy
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/bundler-1.2.0/lib/bundler/rubygems_integration.rb:147:in
block in replace_gem': heroku is not part of the bundle. Add it to
Gemfile. (Gem::LoadError)
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/heroku:18:in'
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval'
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32
/bin/ruby_noexec_wrapper:14:in'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/bundler-1.2.0/lib/bundler/rubygems_integration.rb:147:in
block in replace_gem': heroku is not part of the bundle. Add it to
Gemfile. (Gem::LoadError)
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/heroku:18:in'
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval'
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32
/bin/ruby_noexec_wrapper:14:in'
rake aborted!
Command failed with status (1): [heroku run rake db:migrate --app
admin-staging-fresca]
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/stage.rb:148:in
sh_heroku'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32
/gems/heroku_san-4.0.4/lib/heroku_san/stage.rb:51:inrun'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/deploy/rails.rb:9:in
deploy'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32
/gems/heroku_san-4.0.4/lib/heroku_san/stage.rb:66:indeploy'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/tasks.rb:209:in
block (3 levels) in <top (required)>'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32
/gems/heroku_san-4.0.4/lib/heroku_san/project.rb:66:inblock in each_app'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/project.rb:65:in
each'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32
/gems/heroku_san-4.0.4/lib/heroku_san/project.rb:65:ineach_app'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.4/lib/heroku_san/tasks.rb:321:in
each_heroku_app'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32
/gems/heroku_san-4.0.4/lib/heroku_san/tasks.rb:208:inblock (2 levels) in '
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32
/bin/ruby_noexec_wrapper:14:in'
Tasks: TOP => deploy => heroku:deploy
(See full trace by running task with --trace)—
Reply to this email directly or view it on GitHubhttps://github.com//issues/108#issuecomment-10656699.
Yes, heroku_san 4.0.4 with latest version of Heroku tool belt installed.
For temporary, we had to install heroku gem on development environment.
Is this ticket dead? Or should I create a new ticket?
I haven't been able to catch up on this -- but the latest version of
heroku_san (4.0.7) should work okay. If it doesn't then there's still a bug
and just +1 this issue.
On Mon, Dec 3, 2012 at 11:20 PM, Dano Lee notifications@github.com wrote:
Is this ticket dead? Or should I create a new ticket?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/108#issuecomment-10986833.
4.0.7 shows the same error.
git update-ref -d refs/heroku_san/deploy
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/bundler-1.2.0/lib/bundler/rubygems_integration.rb:147:in block in replace_gem': heroku is not part of the bundle. Add it to Gemfile. (Gem::LoadError) from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/heroku:18:in
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval' from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/bundler-1.2.0/lib/bundler/rubygems_integration.rb:147:in
block in replace_gem': heroku is not part of the bundle. Add it to Gemfile. (Gem::LoadError) from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/heroku:18:in
'from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval' from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
'rake aborted!
Command failed with status (1): [heroku run rake db:migrate --app www-staging-fresca]
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:147:in
sh_heroku' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:48:in
run'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/deploy/rails.rb:9:in
deploy' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:63:in
deploy'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:209:in
block (3 levels) in <top (required)>' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:63:in
block in each_app'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:62:in
each' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:62:in
each_app'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:321:in
each_heroku_app' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:208:in
block (2 levels) in <top (required)>'/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
eval' /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in
'Tasks: TOP => deploy => heroku:deploy
(See full trace by running task with --trace)
Try removing the old heroku gem from the gem set:
gem uninstall heroku
I think that heroku_san is running the wrong CLI because gems come before /usr/bin
in the search PATH
If that resolves your problem, I can add a fall back to sh_heroku
I'll try to replicate it on my laptop, too
Sent from my iPhone ~ 808.722.6142
On Dec 4, 2012, at 10:47 PM, Dano Lee notifications@github.com wrote:
4.0.7 shows the same error.
git update-ref -d refs/heroku_san/deploy
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/bundler-1.2.0/lib/bundler/rubygems_integration.rb:147:in block in replace_gem': heroku is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/heroku:18:in'
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in eval'
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/bundler-1.2.0/lib/bundler/rubygems_integration.rb:147:in block in replace_gem': heroku is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/heroku:18:in'
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in eval'
from /Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in'
rake aborted!
Command failed with status (1): [heroku run rake db:migrate --app www-staging-fresca]
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:147:in sh_heroku'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:48:inrun'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/deploy/rails.rb:9:in deploy'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/stage.rb:63:indeploy'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:209:in block (3 levels) in <top (required)>'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:63:inblock in each_app'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:62:in each'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/project.rb:62:ineach_app'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:321:in each_heroku_app'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/gems/heroku_san-4.0.7/lib/heroku_san/tasks.rb:208:inblock (2 levels) in '
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in eval'
/Users/danolee/.rvm/gems/ruby-1.9.3-p194@rails32/bin/ruby_noexec_wrapper:14:in'
Tasks: TOP => deploy => heroku:deploy
(See full trace by running task with --trace)—
Reply to this email directly or view it on GitHub.
This was a problem a colleague was having, and 'gem uninstall heroko' (not bundle exec) on the machine sorted it out.