AccessDenied for https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/heroku-buildpack-static.tgz

[Nikita Fedyashev]

Steps to reproduce:

create a new app, set a buildpack using web interface, enter "heroku/heroku-buildpack-static"

it is saved like
https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/heroku-buildpack-static.tgz

<Error>
  <Code>AccessDenied</Code>
  <Message>Access Denied</Message>
  <RequestId>EQAJ5R7Q3K9S1J9G</RequestId>
  <HostId>fY0gHYj7E6rDEjDLB3RW9pDeB6kVrmSzBWOEXcH3QBAfuQY+Vewz/9bn0h8K2R1U+KwunoTIG/k=</HostId>
</Error>

---

remote:  !     error fetching custom buildpack https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/heroku-buildpack-static.tgz
remote: 
remote:  !     Push failed

Other buildpacks seem to work fine, e.g. my other buildpack is

https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku-community/multi-procfile.tgz(originally saved as "heroku-community/multi-procfile")

Update: If buildpack is set as "https://github.com/heroku/heroku-buildpack-static.git" it works fine, so the issue must be in some component that transforms "heroku/heroku-buildpack-static" buildpack slug into inaccessible registry URL.

[Ed Morley]

Hi! The build system error message should really make this clearer (I'll file a ticket in our backlog), but this is failing because a buildpack of that name does not exist.

The buildpack registry short names are independent of the GitHub repo name - and are quite often not the same (and many buildpacks are not on buildpack registry, so only usable via the GitHub URL).

The buildpack registry name of this buildpack was missing from the README - I've just added it in #194.

The best way to find out if a buildpack is in the registry is via the search command, eg:

$ heroku plugins:install buildpack-registry
$ heroku buildpacks:search static
Buildpack                    Category   Description
───────────────────────────  ─────────  ───────────────────────────────────
heroku-community/static      languages  Heroku buildpack for handling stat…
...

12 buildpacks found

See more at:
https://devcenter.heroku.com/articles/buildpack-registry