Skip to content

Instantly share code, notes, and snippets.

@hunterloftis

hunterloftis/gist:1e42a29491330f89ae36

Created August 24, 2015 18:06
Show Gist options
  • Save hunterloftis/1e42a29491330f89ae36 to your computer and use it in GitHub Desktop.
Save hunterloftis/1e42a29491330f89ae36 to your computer and use it in GitHub Desktop.
Download ZIP
problems with CLI buildpacks array manipulation
Raw
gistfile1.md
  1. The add/set commands are ambiguous and confusing
  2. Forking/cloning requires a sometimes-long sequence of tedious add/set/clear commands
  3. The list of buildpacks isn't carried with the files in a repo

what does buildpacks:set do?

Can you set the whole list at once, eg heroku buildpacks:set url1, url2, url3? Or does it only set the final buildpack? If you have a previously defined list, what does :set do? Does it replace the final buildpack, or blow away the whole list, or error?

what does buildpacks:add do?

Does it add to the beginning or the end of the list? When you add with an --index, is it indexing from zero or from one?

@jkutner
Copy link

jkutner commented Aug 24, 2015

Proposal

These things together might solve the problems:

Pinned buildpacks: once a buildpack is pushed, it gets the detected buildpack set on it.

heroku buildpacks:import - imports buildpacks from app.json. overwrites existing buildpacks.

Incorporate app.json into detection logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment