Emily Casey
Emily Casey
👋 I work as maintainer on both the Cloud Native Buildpacks project and [Paketo](https://paketo.io/) which provides buildpack implementations for a variety of runtimes including Java (https://github.com/aws/apprunner-roadmap/issues/16) and Golang (https://github.com/aws/apprunner-roadmap/issues/10). Happy...
@hariohmprasath 👋! Happy to hear this integration is potentially going forward, we are excited to help however we can :). In addition to the communication channels @samj1912 mentioned for the...
Because `rebaser` doesn't accept a `-layers` flag I think we should probably just back to a non-relative default path. The question is, which path? Before API 0.5, the default was...
> @ekcasey, why can't we just add the `-layers` flags to the `rebaser`? We could. I was initially hesitant because the `rebaser` the rebaser has no other use for `-layers`...
The spec required that the lifecycle does not modify the value of `$HOME` and instead respects the values provided by the stack images. I could see an argument for explicitly...
@schneems > In addition, I would like to propose some possible future changes to the spec: > > Make env vars using prepend and append an error unless a delimiter...
@schneems and @dmikusa-pivotal You make some good points. I would prefer requiring a delimiter to changing the default b/c 1. If buildpack authors miss the warnings (say for example they...
@micahyoung Do we need a cross-platform solution for this? We will only need to convert the string to the binary format on windows right, and therefore we can use the...
@micahyoung good point, I was only thinking about the lifecycle/spec use case. I forgot that the platform reads and uses these env vars. `create-builder` needs to set file ownership (`package-buildpack`...
@micahyoung Given that this isn't perfectly straight forward, it is probably worth doing a proof-of-concept before committing to a strategy in the spec. I am going to reschedule this from...