siassaj / heroku-buildpack-git-deploy-keys Goto Github PK

Hello,
thanks for the useful buildpack. Unfortunately, it stopped working for me suddenly. My assumption is that it has to do with the new introduced heroku-16 stack. Worked fine with the cedar-14 stack.

With the heroku-16 stack, I always get the error !!!! GIT_DEPLOY_KEY was invalid even though there is a valid key within the environment variable

I worked fine yesterday. Now I'm getting

=====> Downloading Buildpack: https://github.com/siassaj/heroku-buildpack-git-deploy-keys
=====> Detected Framework: Git Deploy Keys
:::::> ############################################
:::::>          GIT DEPLOY KEY BUILDPACK
:::::> ############################################
:::::> ssh dir is /app/.ssh
:::::> Using Multiple Keys
       !!!! GITHUB_DEDLOY_KEY(S) not set
       !!!!   Try `heroku config:add GITHUB_DEPLOY_KEY(S)=<your private token(s)>`

 !     Push rejected, failed to compile Multipack app

The config is apparently added.

My name is Jon Byrum and I’m a product manager at Heroku. Your buildpack is one of the top 200 most popular buildpacks on Heroku!

I would like to invite you to publish your buildpack early in our Buildpack Registry, before it is made available to the general public (expected early July).

To register your buildpack, visit: https://addons-next.heroku.com/buildpacks
Documentation: https://devcenter.heroku.com/articles/buildpack-registry

Why register?

• By registering early you’ll be able to grab your preferred namespace for the buildpack
• After registering, your buildpack will be available to all Heroku users when they run heroku buildpacks:search. In the future, we will only display registered buildpacks on elements.heroku.com/buildpacks
• The Buildpack Registry makes it easy for you to publish a new version of your buildpack, as well as roll back if there are errors

Recommended naming conventions:

• We recommend that you use the same namespace (e.g., jbyrum) with Buildpack Registry that you use on GitHub
• In general, avoid using "buildpack" in the name of your registered buildpack
  • For example: If your Github repo is github.com/foobar/heroku-buildpack-elixir, then we recommend a name like "foobar/elixir"

It would be greatly appreciated if you could publish before June 18th, as we prepare to make the feature publicly available. Registering a buildpack should take approximately 5 minutes.

If you have any questions about registering (or run into any issues), please email:
[email protected]

Hi!

The Heroku-22 stack was just released:
https://devcenter.heroku.com/changelog-items/2429

In Heroku-22, there is no longer a system install of Ruby:
https://devcenter.heroku.com/articles/heroku-22-stack#system-ruby-is-no-longer-installed

This buildpack is written entirely in Ruby, and so in order for this buildpack to work on Heroku-22, one of the following will be necessary:

1. Have the buildpack vendor Ruby for use by this script (for an example of a buildpack doing this, see heroku/heroku-buildpack-nginx#103).
2. Convert the buildpack to use shell/bash scripts instead.
3. Have users of this buildpack add the heroku/ruby buildpack prior to this one (they will also need to add a minimal Gemfile to their app source, if not already present, so the Ruby buildpack passes detection).