Skip to content
This repository has been archived by the owner on Jun 18, 2020. It is now read-only.

Let's extend the lifecycle to make it easier to wrap v3 buildpacks so they can be used on v2a/v2b platforms. #1

Closed
ssisil opened this issue Oct 4, 2018 · 0 comments

Comments

@ssisil
Copy link

ssisil commented Oct 4, 2018

Add the following lifecycle inputs:

  1. -launch, $PACK_LAUNCH_DIR, default in stack images: /workspace
  2. -cache, $PACK_CACHE_DIR, default in stack images: /cache
  3. -app, $PACK_APP_DIR, default in stack images: /workspace/app

Notes

  • logic on launcher.go:29 should whitelist buildpack IDs, or something like that
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants