Emily Casey

@micahyoung Sounds like a plan. I made a placeholder spec issue https://github.com/buildpacks/spec/issues/129 for this. It seem like nothing proposed here is in danger of being impossible (?) and you are...

@poy It is not currently possible, but it is something we could specify/implement in the future if there is sufficient interest. Would you be comfortable sharing your use case?

@poy Would you be providing inputs images (i.e the run-image and previous image) as tarballs as well?

I think we should do this for the phases for which a platform would typically use the lifecycle image: `analyze`, `restore`, `export`, and `rebase`. But not `detect`, `build`, `create` or...

Just brainstorming a few more alternatives: 1. Log this at the debug level. Folks can find the info if they have questions but it won't be in your face on...

@sclevine These labels were added to the Platform API spec in `0.3`. I think this should begin with a PR to the spec to update the label schema.

@jromero why not add templates for new APIs in advance of support in all suggested builders? Users can still choose an older API template right?

@jromero I failed at tabs and posted that in the wrong issue I think, apologies

The only reference in the docs currently is here https://buildpacks.io/docs/create-buildpack/building-blocks-cnb/. It's purpose isn't well described, nor do we have a good documentation around which version of the buildpack interface /...

@natalieparellano Assuming we made the changes described in #339, I think we would want to add this additional keychain to the end of our `MultiKeychain`.